Httpfy

DNS Report for sqrx.com

Date Generated: 2024-09-01 23:41:25

Nameservers

  • ns1fkl.name.com
    • IPv4: 163.114.216.17
    • IPv6: 2a00:edc0:107::1
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • ns2hjl.name.com
    • IPv4: 163.114.216.49
    • IPv6: 2402:cf80:107::1
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • ns3hjx.name.com
    • IPv4: 163.114.217.17
    • IPv6: 2a00:edc0:107::49
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • ns4sxy.name.com
    • IPv4: 163.114.217.49
    • IPv6: 2402:cf80:107::49
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A

Nameserver Count - OK

Nameserver Queries

  • ns1fkl.name.com
    • Status: Responded
    • IP(s): 216.239.32.21, 216.239.34.21, 216.239.36.21, 216.239.38.21
    • TTL: 300 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns2hjl.name.com
    • Status: Responded
    • IP(s): 216.239.32.21, 216.239.34.21, 216.239.36.21, 216.239.38.21
    • TTL: 300 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns3hjx.name.com
    • Status: Responded
    • IP(s): 216.239.32.21, 216.239.34.21, 216.239.36.21, 216.239.38.21
    • TTL: 300 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)
  • ns4sxy.name.com
    • Status: Responded
    • IP(s): 216.239.32.21, 216.239.34.21, 216.239.36.21, 216.239.38.21
    • TTL: 300 seconds
    • Recursive Queries: Does not allow recursive queries
    • TCP Connectivity: TCP connection failed (Response code: REFUSED)

SOA Records

ns1fkl.name.com
  • Serial: 1674118493
  • Refresh: 43200
  • Retry: 7200
  • Expire: 1209600
  • Minimum TTL: 3600
ns2hjl.name.com
  • Serial: 1674118493
  • Refresh: 43200
  • Retry: 7200
  • Expire: 1209600
  • Minimum TTL: 3600
ns3hjx.name.com
  • Serial: 1674118493
  • Refresh: 43200
  • Retry: 7200
  • Expire: 1209600
  • Minimum TTL: 3600
ns4sxy.name.com
  • Serial: 1674118493
  • Refresh: 43200
  • Retry: 7200
  • Expire: 1209600
  • Minimum TTL: 3600

Serial: 1674118493 - OK

REFRESH: 43200 - OK

RETRY: 7200 - OK

EXPIRE: 1209600 - OK

MINIMUM TTL: 3600 - OK

MX Records

ns1fkl.name.com
ns2hjl.name.com
ns3hjx.name.com
ns4sxy.name.com

MX Record Consistency - Warning: Inconsistencies found

MX Record Count - OK

Reverse MX A records (PTR)

  • 26.63.253.172.in-addr.arpa -> bi-in-f26.1e100.net
  • 27.167.251.142.in-addr.arpa -> ww-in-f27.1e100.net
  • 26.153.250.142.in-addr.arpa -> ea-in-f26.1e100.net
  • 26.184.233.64.in-addr.arpa -> wa-in-f26.1e100.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
  • 26.202.85.209.in-addr.arpa -> dg-in-f26.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:_spf.google.com ~all
  • SPF Syntax: Passed
  • Deprecated Elements: Passed
  • IP Addresses:
  • Includes: _spf.google.com
  • DNS Lookups: 2
  • Void Lookups: Passed
  • Escaping Chars: Not Present
  • All Mechanism: ~all

DKIM (DomainKeys Identified Mail)

  • DKIM Records Found: Yes
  • Selectors Found: google
  • Selector 'google':
    Record: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkiFIkXcG0AIrtRpG8EXtFT4U2ZFFkLoNW3kAHKdSKY7qowSi73vTiDW3nWbEUGao6hqS4r76pKCJ2jpljOF8JNgmzLl/cCNhQI++Hs+Jrzl1Z9ycBxRn1o6ZjJE9xw8dZlTdSb2tDRCLDM22N7vuMk581HNhj3Sb/QqnjgN8eNH3c1ug2MF/LE/WyOizzwUHH
  • Valid Syntax: Yes

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