sfmta.com

Checked 22 October 2026, 10:41 UTC · via 8.8.8.8
!Passed with warnings
27 passed 1 warning 0 failed 3 info

Registration

info

.com generic · CSC Corporate Domains, Inc. · expires 2027-02-13

Found

TLD
.com (generic)
ICANN policies apply
yes
Registrar
CSC Corporate Domains, Inc.
Registered
13 February 2004
Last changed
9 February 2026
Expires
13 February 2027
Status
client transfer prohibited
Registry nameservers
ns1-06.azure-dns.com, ns2-06.azure-dns.net, ns3-06.azure-dns.org, ns4-06.azure-dns.info
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-02-13 #3
    The registration is valid until 2027-02-13 (114 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

info

ns1-06.azure-dns.com, ns2-06.azure-dns.net, ns3-06.azure-dns.org, ns4-06.azure-dns.info

Found

Parent zone
com
Delegation from
a.gtld-servers.net (192.5.6.30)
NS at the parent
ns1-06.azure-dns.com, ns2-06.azure-dns.net, ns3-06.azure-dns.org, ns4-06.azure-dns.info
NS in the zone
ns1-06.azure-dns.com, ns2-06.azure-dns.net, ns3-06.azure-dns.org, ns4-06.azure-dns.info
NameserverAddressesNetwork (AS)Glue
ns1-06.azure-dns.com13.107.236.6 2603:1061:0:700::6AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US13.107.236.6 2603:1061:0:700::6
ns2-06.azure-dns.net150.171.21.6 2620:1ec:8ec:700::6AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns3-06.azure-dns.org204.14.183.6 2a01:111:4000:700::6AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-
ns4-06.azure-dns.info208.84.5.6 2620:1ec:bda:700::6AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US AS8075 MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1-06.azure-dns.com, ns2-06.azure-dns.net, ns3-06.azure-dns.org, ns4-06.azure-dns.info.
  • ✓ 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 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US): 8 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.
    #11
  • ✓ Nameserver names under 4 TLDs #12
    Nameserver names use the TLDs .com, .info, .net, .org.
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1-06.azure-dns.com 13.107.236.6NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns1-06.azure-dns.com 2603:1061:0:700::6NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns2-06.azure-dns.net 150.171.21.6NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns2-06.azure-dns.net 2620:1ec:8ec:700::6NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-06.azure-dns.org 204.14.183.6NOERROR, 4 ms, authoritativenoyes / yesrefused-
ns3-06.azure-dns.org 2a01:111:4000:700::6NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns4-06.azure-dns.info 208.84.5.6NOERROR, 5 ms, authoritativenoyes / yesrefused-
ns4-06.azure-dns.info 2620:1ec:bda:700::6NOERROR, 4 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 8 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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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 2017050488 · primary ns1-06.azure-dns.com

Found

Primary (MNAME)
ns1-06.azure-dns.com
Contact (RNAME)
azuredns-hostmaster.microsoft.com
Serial
2017050488
Refresh / retry
3600 s / 300 s
Expire
2419200 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
ns1-06.azure-dns.com (13.107.236.6)2017050488
ns1-06.azure-dns.com (2603:1061:0:700::6)2017050488
ns2-06.azure-dns.net (150.171.21.6)2017050488
ns2-06.azure-dns.net (2620:1ec:8ec:700::6)2017050488
ns3-06.azure-dns.org (204.14.183.6)2017050488
ns3-06.azure-dns.org (2a01:111:4000:700::6)2017050488
ns4-06.azure-dns.info (208.84.5.6)2017050488
ns4-06.azure-dns.info (2620:1ec:bda:700::6)2017050488

Checks

  • ✓ Serial 2017050488 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1h, retry 5m, expire 28d, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1-06.azure-dns.com is one of the listed nameservers.
  • ✓ Contact azuredns-hostmaster@microsoft.com #25
    The SOA RNAME azuredns-hostmaster.microsoft.com means azuredns-hostmaster@microsoft.com.
  • ✓ Date-based serial #26
    The serial 2017050488 follows the YYYYMMDDnn convention (2017-05-04).

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

23 records at the apex

Found

Read from
13.107.236.6:53
TypeValueTTL
SOAns1-06.azure-dns.com. azuredns-hostmaster.microsoft.com. 2017050488 3600 300 2419200 3003600
NSns1-06.azure-dns.com.172800
NSns2-06.azure-dns.net.172800
NSns3-06.azure-dns.org.172800
NSns4-06.azure-dns.info.172800
A23.185.0.2300
AAAA2620:12a:8000::2300
AAAA2620:12a:8001::2300
MX0 sfmta-com.mail.protection.outlook.com.300
TXT"/Rx7ZgIdwetuB7Axp+cZmYCMLg+imcxbS/jzQTzkzbVqWXDeFduJkC9Ksj4Z2ViW+mSd698pXy2uQxhXGYPrFQ=="300
TXT"apple-domain-verification=pWq1cAIbOD9m8Nuo"300
TXT"docusign=7f3c20e7-0e15-4842-ba4b-e96cb64c154a"300
TXT"google-site-verification=Ki3_RxKt3tEWxogHu1nlMqyGn0KAEEy2ekiKZey1Bbs"300
TXT"adobe-idp-site-verification=1c5c0dca7baca33b2e644ba9d6e0c7861f821c8ef1f628eec570fe6240a050c9"300
TXT"onetrust-domain-verification=e28986be9a7d40369e824d1b505553a2"300
TXT"atlassian-domain-verification=o9vh2dpJpiQGnE9NyTGWwuZLfwp74Ksv0vCFhv0WaDdwcmbyDUxy2muJPAqRJAq4"300
TXT"v=spf1 ip4:75.10.230.1 ip4:75.10.230.180 ip4:75.10.230.181 ip4:192.190.32.202 include:spf.protection.outlook.com include:_spf.alchemer.com include:_spf.salesforce.com include:_spf.psm.knowbe4.com include:spf-008a4301.pphosted.com include:spf-009c9501.ppho" "sted.com include:spf-008a4302.pphosted.com include:everbridge.net ~all"300
TXT"MS=ms46368357"300
TXT"MS=ms30300272"300
TXT"nintex.5bd38b830424ae48c9bb8d61"300
TXT"google-gws-recovery-domain-verification=58295218"300
TXT"google-site-verification=5dyfPsMHS7rZax4GJZ0CYa65ox7Oq9ittaeBAbHQid8"300
TXT"_x8wv18shuyl0dkcremajwcx2b0h1yzq"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 5m, AAAA 5m, MX 5m, NS 2d.
  • ✓ No CNAME at the apex #33
    The zone apex has no CNAME record.
  • ✓ No wildcard #34
    Names that don't exist return NXDOMAIN.
  • 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