Httpfy

DNS Report for getmicrosoftkey.com

Date Generated: 2024-08-07 00:50:30

Nameservers

  • ns1-32.azure-dns.com
    • IPv4: 150.171.10.32
    • IPv6: 2603:1061:0:10::20
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • ns2-32.azure-dns.net
    • IPv4: 150.171.16.32
    • IPv6: 2620:1ec:8ec:10::20
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • ns3-32.azure-dns.org
    • IPv4: 13.107.222.32
    • IPv6: 2a01:111:4000:10::20
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • ns4-32.azure-dns.info
    • IPv4: 13.107.206.32
    • IPv6: 2620:1ec:bda:10::20
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A

Nameserver Count - OK

Nameserver Queries

  • ns1-32.azure-dns.com
    • Status: Failed: The DNS response does not contain an answer to the question: getmicrosoftkey.com. IN A
    • IP(s):
    • TTL: N/A seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)
  • ns2-32.azure-dns.net
    • Status: Failed: The DNS response does not contain an answer to the question: getmicrosoftkey.com. IN A
    • IP(s):
    • TTL: N/A seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)
  • ns3-32.azure-dns.org
    • Status: Failed: The DNS response does not contain an answer to the question: getmicrosoftkey.com. IN A
    • IP(s):
    • TTL: N/A seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)
  • ns4-32.azure-dns.info
    • Status: Failed: The DNS response does not contain an answer to the question: getmicrosoftkey.com. IN A
    • IP(s):
    • TTL: N/A seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)

SOA Records

ns1-32.azure-dns.com
  • Serial: 1
  • Refresh: 3600
  • Retry: 300
  • Expire: 2419200
  • Minimum TTL: 300
ns2-32.azure-dns.net
  • Serial: 1
  • Refresh: 3600
  • Retry: 300
  • Expire: 2419200
  • Minimum TTL: 300
ns3-32.azure-dns.org
  • Serial: 1
  • Refresh: 3600
  • Retry: 300
  • Expire: 2419200
  • Minimum TTL: 300
ns4-32.azure-dns.info
  • Serial: 1
  • Refresh: 3600
  • Retry: 300
  • Expire: 2419200
  • Minimum TTL: 300

Serial: 1 - OK

REFRESH: 3600 - OK

RETRY: 300 - OK

EXPIRE: 2419200 - OK

MINIMUM TTL: 300 - Note: Outside recommended range (1-3 hours)

MX Records

ns1-32.azure-dns.com

Error: The DNS response does not contain an answer to the question: getmicrosoftkey.com. IN MX

ns2-32.azure-dns.net

Error: The DNS response does not contain an answer to the question: getmicrosoftkey.com. IN MX

ns3-32.azure-dns.org

Error: The DNS response does not contain an answer to the question: getmicrosoftkey.com. IN MX

ns4-32.azure-dns.info

Error: The DNS response does not contain an answer to the question: getmicrosoftkey.com. IN MX

MX Record Consistency - OK

MX Record Count - OK

Reverse MX A records (PTR)

No PTR records data available.

  • Signed: No
  • Validation: Failed
  • DNSKEY Records: None
  • DS Records in parent zone: None
  • DS at Parent: None

DNSSEC - Note: Domain is not signed with DNSSEC

Error: No DNSSEC records found

SPF (Sender Policy Framework)

SPF Record Published: Failed

Multiple SPF Records: Passed

Errors:
  • No TXT records found

DKIM (DomainKeys Identified Mail)

  • DKIM Records Found: No
Warnings:
  • No DKIM records found for common selectors

DMARC

DMARC External Validation:
  • Valid external domains: rua.agari.com, ruf.agari.com
  • All external domains in your DMARC record are giving permission to send them DMARC reports.
Check DNS for Another Domain

Use our DNS Checker to analyze DNS records for any domain.

Go to DNS Checker