phillymag.com

Checked 22 October 2026, 10:13 UTC · via 8.8.8.8
!Passed with warnings
21 passed 3 warnings 0 failed 7 info

Registration

info

.com generic · DreamHost, LLC · expires 2028-10-08

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
DreamHost, LLC
Registered
9 October 1995
Last changed
4 September 2026
Expires
8 October 2028
Status
client transfer prohibited
Registry nameservers
ns1.innoscale.net, ns2.innoscale.net
RDAP server
https://rdap.verisign.com/com/v1/

Checks

  • i
    .com is a generic TLD (gTLD)
    Generic TLD under an ICANN registry agreement: ICANN-accredited registrars, UDRP and RDAP apply.
    #1
  • ✓ TLD delegated and signed #2
    .com is delegated in the root zone and DNSSEC-signed.
  • ✓ Expires on 2028-10-08 #3
    The registration is valid until 2028-10-08 (716 days).
  • ✓ Transfer locked #4
    Registry status: client transfer prohibited.
  • ✓ Registry and delegation match #5
    The nameservers registered at the registry are the ones published in DNS.

Delegation

warn

ns1.innoscale.net, ns2.innoscale.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.innoscale.net, ns2.innoscale.net
NS in the zone
ns1.innoscale.net, ns2.innoscale.net
NameserverAddressesNetwork (AS)Glue
ns1.innoscale.net204.11.96.10AS19133 BIRD-HOSTING - Bird Hosting Inc., US-
ns2.innoscale.net204.11.102.254AS19133 BIRD-HOSTING - Bird Hosting Inc., US-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.innoscale.net, ns2.innoscale.net.
    #6
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ No glue needed #8
    All nameservers are outside the zone, so no glue records are needed.
  • ✓ All names resolve #9
    Every nameserver name has an address and is not an alias.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 2 IPv4 /24s and 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS19133 (BIRD-HOSTING - Bird Hosting Inc., US): 2 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • i
    All nameserver names under .net
    All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.
    #12
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

info

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.innoscale.net 204.11.96.10NOERROR, 143 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/
ns2.innoscale.net 204.11.102.254NOERROR, 127 ms, authoritativenoyes / yesrefusedServed by PowerDNS - https://www.powerdns.com/

Checks

  • ✓ All respond #14
    All 2 nameserver addresses answered.
  • ✓ All authoritative #15
    Every responding nameserver answers authoritatively for the zone.
  • ✓ No recursion #16
    The nameservers do not answer recursive queries for other domains.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.innoscale.net: "Served by PowerDNS - https://www.powerdns.com/"; ns2.innoscale.net: "Served by PowerDNS - https://www.powerdns.com/".
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✓ TCP supported #19
    All nameservers answer over TCP.
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 2026092504 · primary ns1.innoscale.net

Found

Primary (MNAME)
ns1.innoscale.net
Contact (RNAME)
kfoley.bostonmagazine.com
Serial
2026092504
Refresh / retry
300 s / 300 s
Expire
300 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1.innoscale.net (204.11.96.10)2026092504
ns2.innoscale.net (204.11.102.254)2026092504

Checks

  • ✓ Serial 2026092504 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    refresh 5m is outside 20m–1d; retry 5m should be shorter than refresh 5m; expire 5m is shorter than 7d; secondaries stop answering too soon when the primary is down; expire 5m must be longer than refresh + retry. Current values: refresh 5m, retry 5m, expire 5m, negative TTL 5m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.innoscale.net is one of the listed nameservers.
  • ✓ Contact kfoley@bostonmagazine.com #25
    The SOA RNAME kfoley.bostonmagazine.com means kfoley@bostonmagazine.com.
  • ✓ Date-based serial #26
    The serial 2026092504 follows the YYYYMMDDnn convention (2026-09-25).

DNSSEC

warn

Not signed

Found

Validated by resolver
no

Checks

  • !
    Not signed
    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

Records

info

10 records at the apex

Found

Read from
204.11.96.10:53
TypeValueTTL
SOAns1.innoscale.net. kfoley.bostonmagazine.com. 2026092504 300 300 300 300300
NSns1.innoscale.net.300
NSns2.innoscale.net.300
A71.19.234.34300
MX0 phillymag-com.mail.protection.outlook.com.300
TXT"facebook-domain-verification=p960jo4n78t9ibo3l5pmmy9ctj7c1a"300
TXT"MS=ms87656338"300
TXT"apple-domain-verification=VAqVAmTrBAatrSYT"300
TXT"google-site-verification=bGmcTErDNf55AQj0E-qur_ohHQdVXiim2brlew_QuIw"300
TXT"v=spf1 include:spf.mandrillapp.com include:spf.protection.outlook.com exists:%{i}._spf.inkyphishfence.com -all"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, MX 5m, NS 5m. The NS TTL at the parent is 2d and in the zone 5m; resolvers may use either.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • i
    Wildcard record
    A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.
    #34
  • i
    No CAA records
    Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.
    #35