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


Info: Problems with 3.048.289 Letsencrypt certificates (378.325 accounts). They must be revoked (revocation starts 2020-03-04 20:00 UTC) - see Revoking certain certificates on March 4. Update 2020-03-07: Good news: Mass-revocation is canceled.

This tool: A check (SerialNumber) is added. Letsencrypt has published a list of critical SerialNumbers, this list is checked. See the part "9. Certificates". If there is a warning, renew that certificate and replace the current certificate.




Y

Private IP-Address found

Checked:
02.12.2019 09:44:39


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
registry.dev.ifx.ninja
A
10.100.10.32
No Hostname found
yes
1
0

AAAA

yes


www.registry.dev.ifx.ninja

Name Error
yes
1
0


2. DNSSEC

Info: The Xml-split has triggered some hidden bugs. Now it looks ok.
If root or the top level zone isn't validated, it's buggy.
Both green and your domain is red -> it's your domain.

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 22545, Flags 256



1 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 21.12.2019, 00:00:00 +, Signature-Inception: 30.11.2019, 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: ninja
ninja
2 DS RR in the parent zone found



1 RRSIG RR to validate DS RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 15.12.2019, 05:00:00 +, Signature-Inception: 02.12.2019, 04:00:00 +, KeyTag 22545, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 10551, Flags 256



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



2 RRSIG RR to validate DNSKEY RR found



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 25.12.2019, 10:34:32 +, Signature-Inception: 25.11.2019, 10:34:23 +, KeyTag 10551, Signer-Name: ninja



Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 25.12.2019, 10:34:32 +, Signature-Inception: 25.11.2019, 10:34:23 +, KeyTag 18097, Signer-Name: ninja



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



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



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 18097, DigestType 1 and Digest "QMfLdfCYRYS0ToWl/HfLO/+QUSg=" 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 8, KeyTag 18097, DigestType 2 and Digest "q440o66+Hgv1JN1TdC1gUDMhfhSU4LLMWMQjHUpk25A=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: ifx.ninja
ifx.ninja
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed domain name between the hashed NSEC3-owner and the hashed NextOwner. So the parent zone confirmes the non-existence of a DS RR.Bitmap: NS, DS, RRSIG



0 DNSKEY RR found





Zone: dev.ifx.ninja
dev.ifx.ninja
0 DS RR in the parent zone found

Zone: registry.dev.ifx.ninja
registry.dev.ifx.ninja
0 DS RR in the parent zone found



0 DNSKEY RR found





Zone: www.registry.dev.ifx.ninja
www.registry.dev.ifx.ninja
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.registry.dev.ifx.ninja
  ns-415.awsdns-51.com

registry.dev.ifx.ninja
  ns-415.awsdns-51.com / 4137c4218fd381982699093c4fceac30 -
205.251.193.159
Chicago/Illinois/United States (US) - Amazon.com, Inc.


 
2600:9000:5301:9f00::1
Seattle/Washington/United States (US) - Amazon.com

dev.ifx.ninja
  ns-415.awsdns-51.com

ifx.ninja
  ns-1369.awsdns-43.org / a00e209e3ab6e3e9a5c308e5715d1864 -


  ns-1621.awsdns-10.co.uk / e9c8bad2f1eab4c7333a14b1bb845cb2 -


  ns-415.awsdns-51.com / 2d48f79e9daad54027f3eabd6f139bb0 -


  ns-653.awsdns-17.net / 069d9eacb1c39f187625f2ad12ef56da -

ninja
  demand.alpha.aridns.net.au / dns1.frpar1


  demand.beta.aridns.net.au / dns1.defra1


  demand.delta.aridns.net.au / dns3.frpar1


  demand.gamma.aridns.net.au / dns1.defra1


4. SOA-Entries


Domain:ninja
Zone-Name:
Primary:demand.alpha.aridns.net.au
Mail:hostmaster.donuts.co
Serial:1575275856
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:4


Domain:ifx.ninja
Zone-Name:
Primary:ns-415.awsdns-51.com
Mail:awsdns-hostmaster.amazon.com
Serial:1
Refresh:7200
Retry:900
Expire:1209600
TTL:86400
num Entries:4


Domain:dev.ifx.ninja
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:registry.dev.ifx.ninja
Zone-Name:
Primary:ns-415.awsdns-51.com
Mail:awsdns-hostmaster.amazon.com
Serial:1
Refresh:7200
Retry:900
Expire:1209600
TTL:86400
num Entries:2


Domain:www.registry.dev.ifx.ninja
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







7. Comments


1. General Results, most used to calculate the result

Aname "registry.dev.ifx.ninja" is subdomain, public suffix is "ninja", top-level-domain-type is "generic", tld-manager is "United TLD Holdco Ltd."
Agood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.
Yregistry.dev.ifx.ninja

10.100.10.32
Warning: Private ip address found. No connection possible. There are two types of ip addresses: Worldwide unique, global addresses and private addresses. If you want that other users connect your domain, your domain must have minimal one A- (ipv4) or AAAA- (ipv6) entry with a global ip address. Check https://en.wikipedia.org/wiki/Private_network to understand the details: 10.0.0.0 to 10.255.255.255: Class A - one private net with 16.777.216 adresses

2. DNS- and NameServer - Checks

AGood: Nameserver supports TCP connections: 2 good Nameserver
AGood: Nameserver supports Echo Capitalization: 2 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 2 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 2 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns-415.awsdns-51.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.
Nameserver doesn't pass all EDNS-Checks: ns-415.awsdns-51.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

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: 34727 milliseconds, 34.727 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)

No CertSpotter - CT-Log entries found


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

No CRT - CT-Log entries found


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
registry.dev.ifx.ninja
0

no CAA entry found
1
0
ifx.ninja
0

no CAA entry found
1
0
ninja
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
dev.ifx.ninja

Name Error - The domain name does not exist
1
0
registry.dev.ifx.ninja

ok
1
0
_acme-challenge.registry.dev.ifx.ninja

Name Error - The domain name does not exist
1
0
_acme-challenge.registry.dev.ifx.ninja.dev.ifx.ninja

Name Error - The domain name does not exist
1
0
_acme-challenge.registry.dev.ifx.ninja.registry.dev.ifx.ninja

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=79785184-7814-4705-94c1-77c994c1c4ed


Last Result: https://check-your-website.server-daten.de/?q=registry.dev.ifx.ninja - 2019-12-02 09:44:39


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

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