Httpfy

DNS Report for fout.jp

Date Generated: 2024-08-06 22:22:46

Nameservers

  • use9.akam.net
    • IPv4: 72.246.46.65
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • use1.akam.net
    • IPv4: 72.246.46.64
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • asia1.akam.net
    • IPv4: 95.100.175.64
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • ns1-162.akam.net
    • IPv4: 193.108.91.162
    • IPv6: 2600:1401:2::a2
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • eur2.akam.net
    • IPv4: 95.100.173.64
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A
  • use5.akam.net
    • IPv4: 2.16.40.64
    • IPv6: 2600:1403:a::40
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • ns1-28.akam.net
    • IPv4: 193.108.91.28
    • IPv6: 2600:1401:2::1c
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): 30 seconds
    • Recursive: N/A
  • usw1.akam.net
    • IPv4: 23.61.199.66
    • IPv6: No IPv6 found
    • TTL (IPv4): 30 seconds
    • TTL (IPv6): N/A seconds
    • Recursive: N/A

Nameserver Count - Note: 8 nameservers (recommended: 2-7)

Nameserver Queries

  • use9.akam.net
    • Status: Responded
    • IP(s): 162.159.135.42
    • TTL: 300 seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)
  • use1.akam.net
    • Status: Responded
    • IP(s): 162.159.135.42
    • TTL: 300 seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)
  • asia1.akam.net
    • Status: Responded
    • IP(s): 162.159.135.42
    • TTL: 300 seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)
  • ns1-162.akam.net
    • Status: Responded
    • IP(s): 162.159.135.42
    • TTL: 300 seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)
  • eur2.akam.net
    • Status: Responded
    • IP(s): 162.159.135.42
    • TTL: 300 seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)
  • use5.akam.net
    • Status: Responded
    • IP(s): 162.159.135.42
    • TTL: 300 seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)
  • ns1-28.akam.net
    • Status: Responded
    • IP(s): 162.159.135.42
    • TTL: 300 seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)
  • usw1.akam.net
    • Status: Responded
    • IP(s): 162.159.135.42
    • TTL: 300 seconds
    • Recursive Queries: Unclear (Response code: NXDOMAIN)
    • TCP Connectivity: TCP connection failed (Response code: NXDOMAIN)

SOA Records

use9.akam.net
  • Serial: 1551667762
  • Refresh: 3600
  • Retry: 1800
  • Expire: 3600000
  • Minimum TTL: 900
use1.akam.net
  • Serial: 1551667762
  • Refresh: 3600
  • Retry: 1800
  • Expire: 3600000
  • Minimum TTL: 900
asia1.akam.net
  • Serial: 1551667762
  • Refresh: 3600
  • Retry: 1800
  • Expire: 3600000
  • Minimum TTL: 900
ns1-162.akam.net
  • Serial: 1551667762
  • Refresh: 3600
  • Retry: 1800
  • Expire: 3600000
  • Minimum TTL: 900
eur2.akam.net
  • Serial: 1551667762
  • Refresh: 3600
  • Retry: 1800
  • Expire: 3600000
  • Minimum TTL: 900
use5.akam.net
  • Serial: 1551667762
  • Refresh: 3600
  • Retry: 1800
  • Expire: 3600000
  • Minimum TTL: 900
ns1-28.akam.net
  • Serial: 1551667762
  • Refresh: 3600
  • Retry: 1800
  • Expire: 3600000
  • Minimum TTL: 900
usw1.akam.net
  • Serial: 1551667762
  • Refresh: 3600
  • Retry: 1800
  • Expire: 3600000
  • Minimum TTL: 900

Serial: 1551667762 - OK

REFRESH: 3600 - OK

RETRY: 1800 - OK

EXPIRE: 3600000 - OK

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

MX Records

use9.akam.net
use1.akam.net
asia1.akam.net
ns1-162.akam.net
eur2.akam.net
use5.akam.net
ns1-28.akam.net
usw1.akam.net

MX Record Consistency - Warning: Inconsistencies found

MX Record Count - OK

Reverse MX A records (PTR)

  • 27.184.233.64.in-addr.arpa -> wa-in-f27.1e100.net
  • 26.122.253.172.in-addr.arpa -> bh-in-f26.1e100.net
  • 26.202.85.209.in-addr.arpa -> dg-in-f26.1e100.net
  • 27.202.85.209.in-addr.arpa -> dg-in-f27.1e100.net
  • 26.184.233.64.in-addr.arpa -> wa-in-f26.1e100.net
  • 27.179.251.142.in-addr.arpa -> pd-in-f27.1e100.net
  • 27.184.233.64.in-addr.arpa -> wa-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 a ip4:54.250.147.234 ip4:54.95.92.71 ip4:52.194.95.51 ip4:202.232.238.0/24 include:_spf.google.com include:_spf.salesforce.com include:spf.haihaimail.jp ~all
  • SPF Syntax: Failed
  • Deprecated Elements: Passed
  • IP Addresses: 54.250.147.234, 54.95.92.71, 52.194.95.51, 202.232.238.0/24
  • Includes: _spf.google.com, _spf.salesforce.com, spf.haihaimail.jp
  • DNS Lookups: 9
  • Void Lookups: Passed
  • Escaping Chars: Not Present
  • All Mechanism: ~all
Errors:
  • SPF record syntax is invalid

DKIM (DomainKeys Identified Mail)

  • DKIM Records Found: Yes
  • Selectors Found: google
  • Selector 'google':
    Record: v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAkjIGA31DL+r4LlfeavWcu8w9VYfQkoz37fdg0op11lzYM0137YVaPZ560SRVnWjGrE+w/LZT3mbkeuAMN2ZR2lkb3cR4qCoyIDx8sXwr2+iwGotxeWQyrMPxTRbGpf0E5hvUntdLndQnO4kPnqT/4MzvDzoh0KBUXRRKHXwquWsbeoSR+47oNXUr/ROv1x
  • Valid Syntax: Yes

DMARC

DMARC External Validation:
  • 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