Httpfy

DNS Report for period-calendar.com

Date Generated: 2024-08-16 03:17:10

Nameservers

  • ns-1538.awsdns-00.co.uk
    • IPv4: 205.251.198.2
    • IPv6: 2600:9000:5306:200::1
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • ns-406.awsdns-50.com
    • IPv4: 205.251.193.150
    • IPv6: 2600:9000:5301:9600::1
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • ns-698.awsdns-23.net
    • IPv4: 205.251.194.186
    • IPv6: 2600:9000:5302:ba00::1
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • ns-1497.awsdns-59.org
    • IPv4: 205.251.197.217
    • IPv6: 2600:9000:5305:d900::1
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • ns07.domaincontrol.com
    • IPv4: 97.74.103.4
    • IPv6: 2603:5:2170::4
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • ns08.domaincontrol.com
    • IPv4: 173.201.71.4
    • IPv6: 2603:5:2270::4
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A

Nameserver Count - OK

Nameserver Queries

  • ns-1538.awsdns-00.co.uk
    • Status: Responded
    • IP(s): 52.202.23.131
    • TTL: 1800 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns-406.awsdns-50.com
    • Status: Responded
    • IP(s): 52.202.23.131
    • TTL: 1800 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns-698.awsdns-23.net
    • Status: Responded
    • IP(s): 52.202.23.131
    • TTL: 1800 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns-1497.awsdns-59.org
    • Status: Responded
    • IP(s): 52.202.23.131
    • TTL: 1800 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns07.domaincontrol.com
    • Status: Responded
    • IP(s): 52.202.23.131
    • TTL: 1800 seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)
  • ns08.domaincontrol.com
    • Status: Responded
    • IP(s): 52.202.23.131
    • TTL: 1800 seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)

SOA Records

ns-1538.awsdns-00.co.uk
  • Serial: 1
  • Refresh: 7200
  • Retry: 900
  • Expire: 1209600
  • Minimum TTL: 86400
ns-406.awsdns-50.com
  • Serial: 1
  • Refresh: 7200
  • Retry: 900
  • Expire: 1209600
  • Minimum TTL: 86400
ns-698.awsdns-23.net
  • Serial: 1
  • Refresh: 7200
  • Retry: 900
  • Expire: 1209600
  • Minimum TTL: 86400
ns-1497.awsdns-59.org
  • Serial: 1
  • Refresh: 7200
  • Retry: 900
  • Expire: 1209600
  • Minimum TTL: 86400
ns07.domaincontrol.com
  • Serial: 2024061600
  • Refresh: 28800
  • Retry: 7200
  • Expire: 604800
  • Minimum TTL: 3600
ns08.domaincontrol.com
  • Serial: 2024061600
  • Refresh: 28800
  • Retry: 7200
  • Expire: 604800
  • Minimum TTL: 3600

Serial - Warning: Inconsistent across nameservers

REFRESH - Warning: Inconsistent across nameservers

RETRY - Warning: Inconsistent across nameservers

EXPIRE - Warning: Inconsistent across nameservers

MINIMUM TTL - Warning: Inconsistent across nameservers

MX Records

ns-1538.awsdns-00.co.uk
ns-406.awsdns-50.com
ns-698.awsdns-23.net
ns-1497.awsdns-59.org
ns07.domaincontrol.com
ns08.domaincontrol.com

MX Record Consistency - Warning: Inconsistencies found

MX Record Count - OK

Reverse MX A records (PTR)

  • 114.141.69.216.in-addr.arpa -> osplibsmtp03-v02.prod.phx3.secureserver.net
  • 78.141.69.216.in-addr.arpa -> osplibsmtp01-v02.prod.phx3.secureserver.net
  • 162.141.69.216.in-addr.arpa -> osplibsmtp02-v02.prod.phx3.secureserver.net
  • 27.27.250.142.in-addr.arpa -> ra-in-f27.1e100.net
  • 26.202.85.209.in-addr.arpa -> dg-in-f26.1e100.net
  • 26.184.233.64.in-addr.arpa -> wa-in-f26.1e100.net
  • 71.141.69.216.in-addr.arpa -> osplibsmtp01-v01.prod.phx3.secureserver.net
  • 113.141.69.216.in-addr.arpa -> osplibsmtp03-v01.prod.phx3.secureserver.net
  • 26.27.250.142.in-addr.arpa -> ra-in-f26.1e100.net
  • 27.202.85.209.in-addr.arpa -> dg-in-f27.1e100.net
  • 27.31.250.142.in-addr.arpa -> bj-in-f27.1e100.net
  • 93.5.153.54.in-addr.arpa -> ec2-54-153-5-93.us-west-1.compute.amazonaws.com
  • 27.153.250.142.in-addr.arpa -> ea-in-f27.1e100.net

PTR Records - OK

  • 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: Passed

Multiple SPF Records: Passed

SPF Record 1:
  • Record: v=spf1 include:dc-aa8e722993._spfm.period-calendar.com ~all
  • SPF Syntax: Passed
  • Deprecated Elements: Passed
  • IP Addresses:
  • Includes: dc-aa8e722993._spfm.period-calendar.com
  • DNS Lookups: 6
  • Void Lookups: Passed
  • Escaping Chars: Not Present
  • All Mechanism: ~all

DKIM (DomainKeys Identified Mail)

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

DMARC

  • Record: None
  • Syntax: Invalid
  • Policy: None
  • RUA (Aggregate Reports):
DMARC External Validation:
  • All external domains in your DMARC record are giving permission to send them DMARC reports.
Errors:
  • DMARC record does not exist
Check DNS for Another Domain

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

Go to DNS Checker