SurfaceMap › p › pptv.com

pptv.com

Checked 2026-10-22 10:21 UTC · first added 2026-10-21

!Check could not complete

Domain & DNS

fail

19 passed 4 warn 2 failed

Areas

iRegistration !Delegation ✗Nameservers !SOA !DNSSEC iRecords

Problems

✗

Nameservers not responding

Nameservers · These addresses did not answer, so resolvers waste time on timeouts: dns1.pplive.com (36.155.28.173): read udp 46.225.38.91:33701->36.155.28.173:53: i/o timeout; dns11.pplive.com (36.155.28.173): read udp 46.225.38.91:40010->36.155.28.173:53: i/o timeout; dns12.pplive.com (36.155.28.173): read udp 46.225.38.91:55338->36.155.28.173:53: i/o timeout; dns13.pplive.com (36.155.28.173): read udp 46.225.38.91:41323->36.155.28.173:53: i/o timeout; dns14.pplive.com (36.155.28.173): read udp 46.225.38.91:48907->36.155.28.173:53: i/o timeout; dns15.pplive.com (36.155.28.173): read udp 46.225.38.91:52522->36.155.28.173:53: i/o timeout.

#14
✗

No DNS over TCP

Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: dns1.pplive.com (219.83.168.173): dial tcp 219.83.168.173:53: connect: connection refused; dns11.pplive.com (219.83.168.173): dial tcp 219.83.168.173:53: connect: connection refused; dns12.pplive.com (219.83.168.173): dial tcp 219.83.168.173:53: connect: connection refused; dns13.pplive.com (219.83.168.173): dial tcp 219.83.168.173:53: connect: connection refused; dns14.pplive.com (219.83.168.173): dial tcp 219.83.168.173:53: connect: connection refused; dns15.pplive.com (219.83.168.173): dial tcp 219.83.168.173:53: connect: connection refused.

#19
!

Glue differs from the zone

Delegation · The addresses at the parent (glue) differ from the addresses in the zone: dns1.pplive.com (glue 219.83.168.173, zone 219.83.168.173, 219.83.168.233, 219.83.168.232, 36.155.28.173); dns11.pplive.com (glue 36.155.28.173, zone 219.83.168.233, 36.155.28.173, 219.83.168.232, 219.83.168.173); dns12.pplive.com (glue 36.155.28.173, zone 219.83.168.173, 36.155.28.173, 219.83.168.233); dns13.pplive.com (glue 219.83.168.173, zone 219.83.168.232, 36.155.28.173, 219.83.168.173, 219.83.168.233); dns14.pplive.com (glue 36.155.28.173, zone 219.83.168.173, 36.155.28.173, 219.83.168.233, 219.83.168.232); dns15.pplive.com (glue 219.83.168.173, zone 219.83.168.233, 36.155.28.173, 219.83.168.173, 219.83.168.232). Update the glue at your registrar.

#8
!

No IPv6

Delegation · None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.

#13
!

Unusual SOA timers

SOA · expire 2h46m40s is shorter than 7d; secondaries stop answering too soon when the primary is down; expire 2h46m40s must be longer than refresh + retry. Current values: refresh 5h33m20s, retry 33m20s, expire 2h46m40s, negative TTL 1h.

#23
!

Not signed

DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.

#27

Recent checks

✗

Full report

Domain & DNS report for pptv.com ›

Mail

error

0 passed 1 warn 3 failed 1 errors

lookups failed for mx; results are incomplete

Areas

✗SPF ✗DMARC ✗DKIM !DNSSEC iMX iBIMI

Problems

✗

No DMARC record

DMARC · No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.

#5
✗

No SPF record

SPF · No SPF record was found for this domain. SPF is important for preventing email spoofing. Add an SPF record to specify which servers are authorized to send email for your domain.

#6
✗

No DKIM keys published

DKIM · _domainkey.pptv.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.

#7
!

Not enabled

DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.

#8

Recent checks

Full report

Mail report for pptv.com ›