sched.com

Checked 22 October 2026, 10:34 UTC · via 8.8.8.8
!Passed with warnings
23 passed 4 warnings 0 failed 4 info

Registration

info

.com generic · NameCheap, Inc. · expires 2027-11-14

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
NameCheap, Inc.
Registered
14 November 2001
Last changed
15 October 2026
Expires
14 November 2027
Status
client transfer prohibited
Registry nameservers
ns1.sched.net, ns2.sched.net, ns3.sched.net, ns4.sched.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 2027-11-14 #3
    The registration is valid until 2027-11-14 (387 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.sched.net, ns2.sched.net, ns3.sched.net, ns4.sched.net

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1.sched.net, ns2.sched.net, ns3.sched.net, ns4.sched.net
NS in the zone
ns1.sched.net, ns2.sched.net, ns3.sched.net, ns4.sched.net
NameserverAddressesNetwork (AS)Glue
ns1.sched.net104.237.150.183AS63949 AKAMAI-LINODE-AP - Akamai Connected Cloud, SG-
ns2.sched.net74.207.253.74AS63949 AKAMAI-LINODE-AP - Akamai Connected Cloud, SG-
ns3.sched.net172.233.247.109AS63949 AKAMAI-LINODE-AP - Akamai Connected Cloud, SG-
ns4.sched.net172.237.79.250AS63949 AKAMAI-LINODE-AP - Akamai Connected Cloud, SG-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1.sched.net, ns2.sched.net, ns3.sched.net, ns4.sched.net.
  • ✓ 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 4 IPv4 /24s and 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS63949 (AKAMAI-LINODE-AP - Akamai Connected Cloud, SG): 4 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

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.sched.net 104.237.150.183NOERROR, 91 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.8.3
ns2.sched.net 74.207.253.74NOERROR, 161 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.8.3
ns3.sched.net 172.233.247.109NOERROR, 23 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.8.3
ns4.sched.net 172.237.79.250NOERROR, 182 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.8.3

Checks

  • ✓ All respond #14
    All 4 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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.sched.net: "PowerDNS Authoritative Server 4.8.3"; ns2.sched.net: "PowerDNS Authoritative Server 4.8.3"; ns3.sched.net: "PowerDNS Authoritative Server 4.8.3"; ns4.sched.net: "PowerDNS Authoritative Server 4.8.3". Hide or replace the version string.
    #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

pass

serial 2026092801 · primary ns1.sched.net

Found

Primary (MNAME)
ns1.sched.net
Contact (RNAME)
hostmaster.sched.net
Serial
2026092801
Refresh / retry
3600 s / 600 s
Expire
604800 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1.sched.net (104.237.150.183)2026092801
ns2.sched.net (74.207.253.74)2026092801
ns3.sched.net (172.233.247.109)2026092801
ns4.sched.net (172.237.79.250)2026092801

Checks

  • ✓ Serial 2026092801 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 10m, expire 7d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.sched.net is one of the listed nameservers.
  • ✓ Contact hostmaster@sched.net #25
    The SOA RNAME hostmaster.sched.net means hostmaster@sched.net.
  • ✓ Date-based serial #26
    The serial 2026092801 follows the YYYYMMDDnn convention (2026-09-28).

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

warn

28 records at the apex

Found

Read from
104.237.150.183:53
TypeValueTTL
SOAns1.sched.net. hostmaster.sched.net. 2026092801 3600 600 604800 300300
NSns3.sched.net.300
NSns1.sched.net.300
NSns4.sched.net.300
NSns2.sched.net.300
A172.66.162.3391
A104.20.32.15491
AAAA2606:4700:10::ac42:a22152
AAAA2606:4700:10::6814:209a52
MX10 aspmx3.googlemail.com.300
MX1 aspmx.l.google.com.300
MX10 aspmx2.googlemail.com.300
MX5 alt1.aspmx.l.google.com.300
MX5 alt2.aspmx.l.google.com.300
TXT"v=spf1 a mx include:email.chargebee.com include:servers.mcsv.net include:spf.mandrillapp.com include:_spf.google.com ip4:64.34.82.80/28 include:22154207.spf04.hubspotemail.net include:amazonses.com -all"300
TXT"google-site-verification=SkZzukpNg4F1ccG0VAMqKXwKbISFLNmJmRdT4_q8Hgw"300
TXT"google-site-verification=_nLOALR6vr6lMZ7KZbsIyDR_Pmt10cIpT9YdsFUP-YY"300
TXT"unbounce716033"300
TXT"anthropic-domain-verification-qy0zct=YApJFlSqWIErUoUbsCRhIu2Ng"300
TXT"google-site-verification=3kIWIvNZI9GSZyiq8b4WQnQCMi1LmEUvm39xL7XLkUI"300
TXT"google-site-verification=MI8j6UVFyVaezC1bGtKE1gccG3SLB6EXKRVyXo7Ua3g"300
TXT"MS=ms81222115"300
TXT"google-site-verification=j1h4YHvMgeizRKNusol0tdQnwP7Qt2nHsScUeiWmJJc"300
TXT"stripe-verification=d1fd4aa8c74dce814dda4aebbb7abb10d7e68207321dd0ceac3daf05429f1980"300
TXT"google-site-verification=7qMhhNhdr3bGWEA6OeGW6R8sXDdWjdkv__UEAXbrrnU"300
CAA0 issue "digicert.com"300
CAA0 issue "letsencrypt.org"300
CAA0 issue "pki.goog; cansignhttpexchanges=yes"300

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: A (1m31s), AAAA (52s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 5m; resolvers may use either.
    #32
  • ✓ 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
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: digicert.com, letsencrypt.org, pki.goog.