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



U

No dns entry found - perhaps mistype. Or wrong IDN

Checked:
06.08.2022 01:16:33


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
proxy.bullhill.dev

Name Error
yes
1
0
www.proxy.bullhill.dev

Name Error
yes
1
0


2. DNSSEC

Zone (*)DNSSEC - Informations

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



DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 21.08.2022, 00:00:00 +, Signature-Inception: 31.07.2022, 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: dev
dev
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 60074, DigestType 2 and Digest uULizlrr9i/KWdBXB+bbt5UhHVQNitugLp6J6DNCR4U=



1 RRSIG RR to validate DS RR found



RRSIG-Owner dev., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 18.08.2022, 17:00:00 +, Signature-Inception: 05.08.2022, 16:00:00 +, KeyTag 20826, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 26730, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner dev., Algorithm: 8, 1 Labels, original TTL: 300 sec, Signature-expiration: 26.08.2022, 15:00:57 +, Signature-Inception: 04.08.2022, 15:00:57 +, KeyTag 60074, Signer-Name: dev



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



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 60074, DigestType 2 and Digest "uULizlrr9i/KWdBXB+bbt5UhHVQNitugLp6J6DNCR4U=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: bullhill.dev
bullhill.dev
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 "i4cfjqbcus603r5gt1ih5linbol34sm0" between the hashed NSEC3-owner "i4celeb46a0bhegf152g7v22rnjpbjvj" and the hashed NextOwner "i4ch8mtet59u8hn4mk6tdctepuejfc5o". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner i4celeb46a0bhegf152g7v22rnjpbjvj.dev., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 26.08.2022, 15:00:57 +, Signature-Inception: 04.08.2022, 15:00:57 +, KeyTag 26730, Signer-Name: dev



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "6n3ds9aanpq49o7cm0cdh9382a0jh2n5" as Owner. That's the Hash of "dev" with the NextHashedOwnerName "6n3ke8diomecihu5u44tqrvf0vcgjmkl". So that domain name is the Closest Encloser of "bullhill.dev". Opt-Out: False.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 6n3ds9aanpq49o7cm0cdh9382a0jh2n5.dev., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 26.08.2022, 15:00:57 +, Signature-Inception: 04.08.2022, 15:00:57 +, KeyTag 26730, Signer-Name: dev



The ClosestEncloser says, that "*.dev" with the Hash "l7bgso866mogtobk9n5u4q5a40l48bao" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "l7auot3t1v77dto2r6hbfqbpretesloe" and the Next Owner "l7bocvbdsl0qrdqmtbkit6q20ivluhjj", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: False.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner l7auot3t1v77dto2r6hbfqbpretesloe.dev., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 26.08.2022, 15:00:57 +, Signature-Inception: 04.08.2022, 15:00:57 +, KeyTag 26730, Signer-Name: dev

Zone: proxy.bullhill.dev
proxy.bullhill.dev
0 DS RR in the parent zone found



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "6n3ds9aanpq49o7cm0cdh9382a0jh2n5" as Owner. That's the Hash of "dev" with the NextHashedOwnerName "6n3ke8diomecihu5u44tqrvf0vcgjmkl". So that domain name is the Closest Encloser of "proxy.bullhill.dev". Opt-Out: False.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 6n3ds9aanpq49o7cm0cdh9382a0jh2n5.dev., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 26.08.2022, 15:00:57 +, Signature-Inception: 04.08.2022, 15:00:57 +, KeyTag 26730, Signer-Name: dev



The ClosestEncloser says, that "*.dev" with the Hash "l7bgso866mogtobk9n5u4q5a40l48bao" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "l7auot3t1v77dto2r6hbfqbpretesloe" and the Next Owner "l7bocvbdsl0qrdqmtbkit6q20ivluhjj", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: False.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner l7auot3t1v77dto2r6hbfqbpretesloe.dev., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 26.08.2022, 15:00:57 +, Signature-Inception: 04.08.2022, 15:00:57 +, KeyTag 26730, Signer-Name: dev

Zone: www.proxy.bullhill.dev
www.proxy.bullhill.dev
0 DS RR in the parent zone found



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "6n3ds9aanpq49o7cm0cdh9382a0jh2n5" as Owner. That's the Hash of "dev" with the NextHashedOwnerName "6n3ke8diomecihu5u44tqrvf0vcgjmkl". So that domain name is the Closest Encloser of "www.proxy.bullhill.dev". Opt-Out: False.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner 6n3ds9aanpq49o7cm0cdh9382a0jh2n5.dev., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 26.08.2022, 15:00:57 +, Signature-Inception: 04.08.2022, 15:00:57 +, KeyTag 26730, Signer-Name: dev



The ClosestEncloser says, that "*.dev" with the Hash "l7bgso866mogtobk9n5u4q5a40l48bao" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "l7auot3t1v77dto2r6hbfqbpretesloe" and the Next Owner "l7bocvbdsl0qrdqmtbkit6q20ivluhjj", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: False.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner l7auot3t1v77dto2r6hbfqbpretesloe.dev., Algorithm: 8, 2 Labels, original TTL: 300 sec, Signature-expiration: 26.08.2022, 15:00:57 +, Signature-Inception: 04.08.2022, 15:00:57 +, KeyTag 26730, Signer-Name: dev


3. Name Servers

DomainNameserverNS-IP
www.proxy.bullhill.dev
  ns-tld1.charlestonroadregistry.com

proxy.bullhill.dev
  ns-tld1.charlestonroadregistry.com

bullhill.dev
  ns-tld1.charlestonroadregistry.com

dev
  ns-tld1.charlestonroadregistry.com


  ns-tld2.charlestonroadregistry.com


  ns-tld3.charlestonroadregistry.com


  ns-tld4.charlestonroadregistry.com


  ns-tld5.charlestonroadregistry.com


4. SOA-Entries


Domain:dev
Zone-Name:dev
Primary:ns-tld1.charlestonroadregistry.com
Mail:cloud-dns-hostmaster.google.com
Serial:1
Refresh:21600
Retry:3600
Expire:259200
TTL:300
num Entries:5


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


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


Domain:www.proxy.bullhill.dev
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 "proxy.bullhill.dev" is subdomain, public suffix is ".dev", top-level-domain is ".dev", top-level-domain-type is "generic", tld-manager is "Charleston Road Registry Inc.", num .dev-domains preloaded: 12 (complete: 175327)
Agood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
AExcellent: Main Domain is in the Google-Preload-List
AExcellent: Main Domain is in the Mozilla/Firefox-Preload-List
AHSTS-Preload-Status: Preloaded. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.

2. DNS- and NameServer - Checks

A
A
AInfo:: 5 different Name Servers found: ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, 5 Name Servers included in Delegation: ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, 5 Name Servers included in 1 Zone definitions: ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, 1 Name Servers listed in SOA.Primary: ns-tld1.charlestonroadregistry.com.
AGood: Only one SOA.Primary Name Server found.: ns-tld1.charlestonroadregistry.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns-tld1.charlestonroadregistry.com.
AGood: All Name Server Domain Names have a Public Suffix.
A
Nameserver doesn't pass all EDNS-Checks: ns-tld1.charlestonroadregistry.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-tld1.charlestonroadregistry.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-tld1.charlestonroadregistry.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

Info: Creating a Letsencrypt certificate with that domain name isn't possible. To create a certificate you need a registered, worldwide unique domain name. The domain name ends with a public suffix, that's good (not Grade Z). But the domain isn't registered. If you want a certificate with that domain name, you have to proof that you are the domain owner. 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: 24950 milliseconds, 24.950 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" > of the last months are listed

Issuerlast 7 daysactivenum Certs
CN=E1, O=Let's Encrypt, C=US
0
1
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
7277037281
leaf cert
CN=E1, O=Let's Encrypt, C=US
2022-08-05 20:10:36
2022-11-03 21:10:35
*.bullhill.dev, bullhill.dev
2 entries



11. Html-Content - Entries

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


12. Nameserver - IP-Adresses

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


No NameServer - IP address - Informations found


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
dev
0

no CAA entry found
1
0


14. TXT - Entries

No TXT entries found


15. DomainService - Entries (SSHFP Check is new - 2022-09-24, may be incomplete, alpha, some results are required)

No DomainServiceEntries entries found



16. Cipher Suites

No Ciphers found


17. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.



Permalink: https://check-your-website.server-daten.de/?i=80e11eed-7c05-49fb-bc23-d656eac4c14f


Last Result: https://check-your-website.server-daten.de/?q=proxy.bullhill.dev - 2022-08-06 01:16:33


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

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

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro