Check DNS, Urls + Redirects, Certificates and Content of your Website


Update: 2020-03-04 - now 90 days later. All affected Letsencrypt certificates should be renewed. Time to remove that Info.




T

Timeout

Checked:
22.01.2020 16:57:10


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
fleet.org
A
216.184.25.12
Albuquerque/New Mexico/United States (US) - Southwest Cyberport, Inc.
Hostname: fleet.org
yes
1
0

A
216.184.25.12
Albuquerque/New Mexico/United States (US) - Southwest Cyberport, Inc.
Hostname: fleet.org
yes
1
0

AAAA

yes


www.fleet.org
C
mail.fleet.org
yes
1
0

A
65.102.98.65
Albuquerque/New Mexico/United States (US) - CenturyLink
Hostname: mail.fleet.org
yes



2. DNSSEC

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



Status: Valid because published



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 33853, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.02.2020, 00:00:00, Signature-Inception: 21.01.2020, 00:00:00, KeyTag 20326, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: org
org
2 DS RR in the parent zone found



2 RRSIG RR to validate DS RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 04.02.2020, 05:00:00, Signature-Inception: 22.01.2020, 04:00:00, KeyTag 33853, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 33853 used to validate the DS RRSet in the parent zone



4 DNSKEY RR found



Public Key with Algorithm 7, KeyTag 9278, Flags 256



Public Key with Algorithm 7, KeyTag 9795, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 7, KeyTag 17883, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 7, KeyTag 63887, Flags 256



3 RRSIG RR to validate DNSKEY RR found



Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 07.02.2020, 15:28:10, Signature-Inception: 17.01.2020, 14:28:10, KeyTag 9278, Signer-Name: org



Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 07.02.2020, 15:28:10, Signature-Inception: 17.01.2020, 14:28:10, KeyTag 9795, Signer-Name: org



Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 07.02.2020, 15:28:10, Signature-Inception: 17.01.2020, 14:28:10, KeyTag 17883, Signer-Name: org



Status: Good - Algorithmus 7 and DNSKEY with KeyTag 9278 used to validate the DNSKEY RRSet



Status: Good - Algorithmus 7 and DNSKEY with KeyTag 9795 used to validate the DNSKEY RRSet



Status: Good - Algorithmus 7 and DNSKEY with KeyTag 17883 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 9795, DigestType 1 and Digest "Nk36s9ryVMq0d7VnWxB2bdqiSYI=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 9795, DigestType 2 and Digest "OSKzG286TqkrGet7UhIPAx/Y4F/wsDuvz5+JG/5/+OU=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: fleet.org
fleet.org
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "7di2vc8on0l627j39r7ih6u1nbnibguj" between the hashed NSEC3-owner "7dhons6hhuaado4b2ndjjlsmnmqsehfa" and the hashed NextOwner "7di35koq7vfg6oqitq2o6k0eue1mnn60". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG Algorithm: 7, 2 Labels, original TTL: 86400 sec, Signature-expiration: 07.02.2020, 15:28:10, Signature-Inception: 17.01.2020, 14:28:10, KeyTag 9278, Signer-Name: org



0 DNSKEY RR found




Zone: www.fleet.org
www.fleet.org
0 DS RR in the parent zone found

Zone: (root)
(root)
1 DS RR published



Status: Valid because published



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 33853, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.02.2020, 00:00:00, Signature-Inception: 21.01.2020, 00:00:00, KeyTag 20326, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: org
org
2 DS RR in the parent zone found



2 RRSIG RR to validate DS RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 04.02.2020, 05:00:00, Signature-Inception: 22.01.2020, 04:00:00, KeyTag 33853, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 33853 used to validate the DS RRSet in the parent zone



4 DNSKEY RR found



Public Key with Algorithm 7, KeyTag 9278, Flags 256



Public Key with Algorithm 7, KeyTag 9795, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 7, KeyTag 17883, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 7, KeyTag 63887, Flags 256



3 RRSIG RR to validate DNSKEY RR found



Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 07.02.2020, 15:28:10, Signature-Inception: 17.01.2020, 14:28:10, KeyTag 9278, Signer-Name: org



Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 07.02.2020, 15:28:10, Signature-Inception: 17.01.2020, 14:28:10, KeyTag 9795, Signer-Name: org



Algorithm: 7, 1 Labels, original TTL: 900 sec, Signature-expiration: 07.02.2020, 15:28:10, Signature-Inception: 17.01.2020, 14:28:10, KeyTag 17883, Signer-Name: org



Status: Good - Algorithmus 7 and DNSKEY with KeyTag 9278 used to validate the DNSKEY RRSet



Status: Good - Algorithmus 7 and DNSKEY with KeyTag 9795 used to validate the DNSKEY RRSet



Status: Good - Algorithmus 7 and DNSKEY with KeyTag 17883 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 9795, DigestType 1 and Digest "Nk36s9ryVMq0d7VnWxB2bdqiSYI=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



Status: Valid Chain of trust. Parent-DS with Algorithm 7, KeyTag 9795, DigestType 2 and Digest "OSKzG286TqkrGet7UhIPAx/Y4F/wsDuvz5+JG/5/+OU=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: fleet.org
fleet.org
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "7di2vc8on0l627j39r7ih6u1nbnibguj" between the hashed NSEC3-owner "7dhons6hhuaado4b2ndjjlsmnmqsehfa" and the hashed NextOwner "7di35koq7vfg6oqitq2o6k0eue1mnn60". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG Algorithm: 7, 2 Labels, original TTL: 86400 sec, Signature-expiration: 07.02.2020, 15:28:10, Signature-Inception: 17.01.2020, 14:28:10, KeyTag 9278, Signer-Name: org



0 DNSKEY RR found




Zone: mail.fleet.org
mail.fleet.org
0 DS RR in the parent zone found



0 DNSKEY RR found




3. Name Servers

DomainNameserverNS-IP
fleet.org
  kitsune.swcp.com
198.59.115.2
Albuquerque/New Mexico/United States (US) - Southwest Cyberport, Inc.


  ns2.swcp.com
216.243.105.246
Albuquerque/New Mexico/United States (US) - Lobo Internet Services

org
  a0.org.afilias-nst.info / ns000b.app14.ams2.afilias-nst.info


  a2.org.afilias-nst.info / 1.fra.pch


  b0.org.afilias-nst.org / ns000b.app26.ams2.afilias-nst.info


  b2.org.afilias-nst.org / 5.fra.pch


  c0.org.afilias-nst.info / app1.iad1.hosts.meta.redstone.afilias-nst.info-2


  d0.org.afilias-nst.org / ns000a.app31.ams2.afilias-nst.info


mail.fleet.org
  swcp.com

fleet.org
  kitsune.swcp.com


  ns2.swcp.com

org
  a0.org.afilias-nst.info / ns000b.app4.ams2.afilias-nst.info


  a2.org.afilias-nst.info / 2.ber.pch


  b0.org.afilias-nst.org / ns000b.app4.ams2.afilias-nst.info


  b2.org.afilias-nst.org / 4.fra.pch


  c0.org.afilias-nst.info / app15.iad1.hosts.meta.redstone.afilias-nst.info-2


  d0.org.afilias-nst.org / ns000b.app5.ams2.afilias-nst.info


4. SOA-Entries


Domain:org
Zone-Name:
Primary:a0.org.afilias-nst.info
Mail:noc.afilias-nst.info
Serial:2013790723
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:6


Domain:fleet.org
Zone-Name:
Primary:swcp.com
Mail:postmaster.mail.swcp.com
Serial:2019121200
Refresh:10800
Retry:3600
Expire:604800
TTL:600
num Entries:2



Domain:org
Zone-Name:
Primary:a0.org.afilias-nst.info
Mail:noc.afilias-nst.info
Serial:2013790723
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:1


Domain:org
Zone-Name:
Primary:a0.org.afilias-nst.info
Mail:noc.afilias-nst.info
Serial:2013790724
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:5


Domain:fleet.org
Zone-Name:
Primary:swcp.com
Mail:postmaster.mail.swcp.com
Serial:2019121200
Refresh:10800
Retry:3600
Expire:604800
TTL:600
num Entries:2


Domain:mail.fleet.org
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks

DomainnameHttp-StatusredirectSec.G
• http://fleet.org/
216.184.25.12
-14

10.026
T
Timeout - The operation has timed out

• http://www.fleet.org/
65.102.98.65
-14

10.050
T
Timeout - The operation has timed out

• https://fleet.org/
216.184.25.12
-14

10.036
T
Timeout - The operation has timed out

• https://www.fleet.org/
65.102.98.65
-14

10.040
T
Timeout - The operation has timed out

• http://fleet.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
216.184.25.12
-14

10.036
T
Timeout - The operation has timed out
Visible Content:

• http://www.fleet.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
65.102.98.65
-14

10.036
T
Timeout - The operation has timed out
Visible Content:

7. Comments


1. General Results, most used to calculate the result

Aname "fleet.org" is domain, public suffix is "org", top-level-domain-type is "generic", tld-manager is "Public Interest Registry (PIR)"
Agood: All ip addresses are public addresses
Agood: No asked Authoritative Name Server had a timeout
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.

2. DNS- and NameServer - Checks

AGood: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: kitsune.swcp.com,ns2.swcp.com
AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
Nameserver doesn't pass all EDNS-Checks: swcp.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

3. Content- and Performance-critical Checks

http://fleet.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 216.184.25.12
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
http://www.fleet.org/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 65.102.98.65
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
ADuration: 138387 milliseconds, 138.387 seconds


8. Connections

No connection informations found. Perhaps only http - connections.


9. Certificates

No certificate informations found. Perhaps only http - connections.


10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0
0
3

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
1358801683
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-01-11 21:03:05
2020-04-10 21:03:05
mail.fleet.org, www.fleet.org - 2 entries


1220344719
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-02 20:12:43
2020-01-31 20:12:43
www.fleet.org - 1 entries


1220344481
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-02 20:12:39
2020-01-31 20:12:39
mail.fleet.org, www.fleet.org - 2 entries



2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > 2019 are listed

Issuerlast 7 daysactivenum Certs
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
0 /0 new
0
3

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
2330599784
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2020-01-11 20:03:05
2020-04-10 19:03:05
mail.fleet.org, www.fleet.org
2 entries


2064854471
precert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-02 19:12:43
2020-01-31 19:12:43
www.fleet.org
1 entries


2064854483
leaf cert
CN=Let's Encrypt Authority X3, O=Let's Encrypt, C=US
2019-11-02 19:12:39
2020-01-31 19:12:39
mail.fleet.org, www.fleet.org
2 entries



11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404


12. Nameserver - IP-Adresses (alpha)

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers:

No NameServer - IP address informations found. The feature is new (2020-05-07), so recheck this domain.


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
mail.fleet.org
0

no CAA entry found
1
0
www.fleet.org



1
0
fleet.org
0

no CAA entry found
1
0

0

no CAA entry found
1
0
org
0

no CAA entry found
1
0

0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
fleet.org

ok
1
0
www.fleet.org


1
0
mail.fleet.org

ok
1
0
_acme-challenge.fleet.org

missing entry or wrong length
1
0
_acme-challenge.www.fleet.org

Name Error - The domain name does not exist
1
0
_acme-challenge.mail.fleet.org

Name Error - The domain name does not exist
1
0
_acme-challenge.fleet.org.fleet.org

perhaps wrong
1
0
_acme-challenge.www.fleet.org.fleet.org

perhaps wrong
1
0
_acme-challenge.www.fleet.org.www.fleet.org

Name Error - The domain name does not exist
1
0
_acme-challenge.mail.fleet.org.mail.fleet.org

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=4af2b71a-c475-4e6c-b782-f9bb12466d95


Last Result: https://check-your-website.server-daten.de/?q=fleet.org - 2020-01-22 16:57:10


Do you like this page? Support this tool, add a link on your page:

<a href="https://check-your-website.server-daten.de/?q=fleet.org" target="_blank">Check this Site: fleet.org</a>