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





1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
demo.lomin.ai

Name Error
yes
1
0
www.demo.lomin.ai

Name Error
yes
1
0
*.lomin.ai
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes


*.demo.lomin.ai
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes



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



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



1 RRSIG RR to validate DNSKEY RR found



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



DS with Algorithm 8, KeyTag 44137, DigestType 2 and Digest eIa9Ne10XcqYPZUaZDSVuSmzp2dqiMaC74jrb+29slM=



1 RRSIG RR to validate DS RR found



RRSIG-Owner ai., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 30.04.2024, 05:00:00 +, Signature-Inception: 17.04.2024, 04:00:00 +, KeyTag 5613, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 17910, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner ai., Algorithm: 8, 1 Labels, original TTL: 3600 sec, Signature-expiration: 22.04.2024, 17:55:42 +, Signature-Inception: 08.04.2024, 16:25:42 +, KeyTag 44137, Signer-Name: ai



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



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

Zone: lomin.ai
lomin.ai
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 "e8etisg9a5g6f7rmc0vhgo71hquj2r2h" between the hashed NSEC3-owner "e8efd8o3sujqjrk3eo5ii2nfoseqo98g" and the hashed NextOwner "e8iu7up9v67tom5o5mm0tlur8b288pv6". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner e8efd8o3sujqjrk3eo5ii2nfoseqo98g.ai., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 28.04.2024, 16:59:40 +, Signature-Inception: 14.04.2024, 15:29:40 +, KeyTag 17910, Signer-Name: ai



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "badg2glv7k64on87uhnkquuf0s14rfr6" as Owner. That's the Hash of "ai" with the NextHashedOwnerName "bamgk787kloha181h09jjf8uudl8jtbi". So that domain name is the Closest Encloser of "lomin.ai". Opt-Out: True.
Bitmap: A, NS, SOA, MX, TXT, RRSIG, DNSKEY, NSEC3PARAM, CDS, CDNSKEY, 63 Validated: RRSIG-Owner badg2glv7k64on87uhnkquuf0s14rfr6.ai., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 28.04.2024, 16:59:40 +, Signature-Inception: 14.04.2024, 15:29:40 +, KeyTag 17910, Signer-Name: ai



0 DNSKEY RR found




Zone: demo.lomin.ai
demo.lomin.ai
0 DS RR in the parent zone found

Zone: www.demo.lomin.ai
www.demo.lomin.ai
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.demo.lomin.ai
  ns-286.awsdns-35.com

demo.lomin.ai
  ns-286.awsdns-35.com

lomin.ai
  ns-1058.awsdns-04.org / e9fac45c500939371cbcfffbdc249869 -
205.251.196.34
Ashburn/Virginia/United States (US) - Amazon.com


 
2600:9000:5304:2200::1
New York/United States (US) - Amazon.com


  ns-1929.awsdns-49.co.uk / 6dcfde66ee367091cda3a1fa185bcea2 -
205.251.199.137
Ashburn/Virginia/United States (US) - Amazon.com


 
2600:9000:5307:8900::1
Seattle/Washington/United States (US) - Amazon.com


  ns-286.awsdns-35.com / 758989b8a91eaa6347c0e27feb0a1605 -
205.251.193.30
Ashburn/Virginia/United States (US) - Amazon.com


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


  ns-630.awsdns-14.net / a41e4c699d0746f11933f1adc7deab05 -
205.251.194.118
Sterling/Virginia/United States (US) - Amazon.com


 
2600:9000:5302:7600::1
Seattle/Washington/United States (US) - Amazon.com

ai
  a.lactld.org / a5-mvd


  anycastdns1-cz.nic.ai


  anycastdns2-cz.nic.ai


  pch.whois.ai / 3.ams.pch


4. SOA-Entries


Domain:ai
Zone-Name:ai
Primary:pch.whois.ai
Mail:vince.offshore.ai
Serial:2024041712
Refresh:3600
Retry:3600
Expire:86400
TTL:86400
num Entries:4


Domain:lomin.ai
Zone-Name:lomin.ai
Primary:ns-286.awsdns-35.com
Mail:awsdns-hostmaster.amazon.com
Serial:1
Refresh:7200
Retry:900
Expire:1209600
TTL:86400
num Entries:8


Domain:demo.lomin.ai
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:www.demo.lomin.ai
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 "demo.lomin.ai" is subdomain, public suffix is ".ai", top-level-domain is ".ai", top-level-domain-type is "country-code", Country is Anguilla, tld-manager is "Government of Anguilla", num .ai-domains preloaded: 218 (complete: 240622)
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.
BNo _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.demo.lomin.ai

2. Header-Checks

U

No https result with http status 2** or 4** (standard-check) found, no header checked.

3. DNS- and NameServer - Checks

AInfo:: 16 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 4 Name Servers.
AInfo:: 16 Queries complete, 16 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 4.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 4 different Name Servers found: ns-1058.awsdns-04.org, ns-1929.awsdns-49.co.uk, ns-286.awsdns-35.com, ns-630.awsdns-14.net, 4 Name Servers included in Delegation: ns-1058.awsdns-04.org, ns-1929.awsdns-49.co.uk, ns-286.awsdns-35.com, ns-630.awsdns-14.net, 4 Name Servers included in 1 Zone definitions: ns-1058.awsdns-04.org, ns-1929.awsdns-49.co.uk, ns-286.awsdns-35.com, ns-630.awsdns-14.net, 1 Name Servers listed in SOA.Primary: ns-286.awsdns-35.com.
AGood: Only one SOA.Primary Name Server found.: ns-286.awsdns-35.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns-286.awsdns-35.com.
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AInfo: Ipv4-Subnet-list: 4 Name Servers, 1 different subnets (first Byte): 205., 1 different subnets (first two Bytes): 205.251., 4 different subnets (first three Bytes): 205.251.193., 205.251.194., 205.251.196., 205.251.199.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 4 Name Servers with IPv6, 1 different subnets (first block): 2600:, 1 different subnets (first two blocks): 2600:9000:, 4 different subnets (first three blocks): 2600:9000:5301:, 2600:9000:5302:, 2600:9000:5304:, 2600:9000:5307:, 4 different subnets (first four blocks): 2600:9000:5301:1e00:, 2600:9000:5302:7600:, 2600:9000:5304:2200:, 2600:9000:5307:8900:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 8 good Nameserver
AGood: Nameserver supports Echo Capitalization: 8 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns-1058.awsdns-04.org / 2600:9000:5304:2200::1: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (057e9537c71ef07d1d1c019fe4851804 -). COOKIE: ok. CLIENTSUBNET: ok.
Nameserver doesn't pass all EDNS-Checks: ns-286.awsdns-35.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-286.awsdns-35.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.

4. 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: 57680 milliseconds, 57.680 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=Amazon RSA 2048 M03, O=Amazon, C=US
0
1
1
CN=Amazon, OU=Server CA 1B, O=Amazon, C=US
0
0
1
CN=Amazon RSA 2048 M01, O=Amazon, C=US
0
0
1

CertSpotter-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
6437861599
precert
CN=Amazon RSA 2048 M03, O=Amazon, C=US
2023-12-26 00:00:00
2025-01-23 23:59:59
demo.lomin.ai - 1 entries


4727946453
precert
CN=Amazon RSA 2048 M01, O=Amazon, C=US
2023-01-25 00:00:00
2024-02-23 23:59:59
demo.lomin.ai - 1 entries


3457334739
precert
CN=Amazon, OU=Server CA 1B, O=Amazon, C=US
2022-02-24 00:00:00
2023-03-25 23:59:59
demo.lomin.ai - 1 entries



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=Amazon RSA 2048 M03, O=Amazon, C=US
0
3
3
CN=Amazon RSA 2048 M01, O=Amazon, C=US
0
0
2
CN=Amazon, OU=Server CA 1B, O=Amazon, C=US
0
0
1
CN=Amazon RSA 2048 M02, O=Amazon, C=US
0
0
1

CRT-IdIssuernot beforenot afterDomain namesLE-Duplicatenext LE
11816719814
precert
CN=Amazon RSA 2048 M03, O=Amazon, C=US
2024-01-20 23:00:00
2025-02-18 22:59:59
*.lomin.ai, lomin.ai
2 entries


11413875405
precert
CN=Amazon RSA 2048 M03, O=Amazon, C=US
2023-12-25 23:00:00
2025-01-23 22:59:59
demo.lomin.ai
1 entries


10091007084
precert
CN=Amazon RSA 2048 M03, O=Amazon, C=US
2023-08-07 22:00:00
2024-09-04 21:59:59
*.lomin.ai, lomin.ai
2 entries


8773039143
precert
CN=Amazon RSA 2048 M02, O=Amazon, C=US
2023-02-28 23:00:00
2023-10-06 21:59:59
*.lomin.ai, lomin.ai
2 entries


8695605169
precert
CN=Amazon RSA 2048 M01, O=Amazon, C=US
2023-02-19 23:00:00
2024-03-20 22:59:59
*.lomin.ai, lomin.ai
2 entries


8490311334
precert
CN=Amazon RSA 2048 M01, O=Amazon, C=US
2023-01-24 23:00:00
2024-02-23 22:59:59
demo.lomin.ai
1 entries


7489540213
precert
CN=Amazon, OU=Server CA 1B, O=Amazon, C=US
2022-09-06 22:00:00
2023-10-06 21:59:59
*.lomin.ai, lomin.ai
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: ns-1058.awsdns-04.org, ns-1929.awsdns-49.co.uk, ns-286.awsdns-35.com, ns-630.awsdns-14.net

QNr.DomainTypeNS used
1
org
NS
l.root-servers.net (2001:500:9f::42)

Answer: a0.org.afilias-nst.info, a2.org.afilias-nst.info, b0.org.afilias-nst.org, b2.org.afilias-nst.org, c0.org.afilias-nst.info, d0.org.afilias-nst.org
2
ns-1058.awsdns-04.org
NS
a0.org.afilias-nst.info (2001:500:e::1)

Answer: g-ns-1031.awsdns-04.org, g-ns-132.awsdns-04.org, g-ns-1604.awsdns-04.org, g-ns-710.awsdns-04.org

Answer: g-ns-1031.awsdns-04.org
205.251.196.7, 2600:9000:5304:700::1

Answer: g-ns-132.awsdns-04.org
205.251.192.132, 2600:9000:5300:8400::1

Answer: g-ns-1604.awsdns-04.org
205.251.198.68, 2600:9000:5306:4400::1

Answer: g-ns-710.awsdns-04.org
205.251.194.198, 2600:9000:5302:c600::1
3
uk
NS
b.root-servers.net (2001:500:200::b)

Answer: dns1.nic.uk, dns2.nic.uk, dns3.nic.uk, dns4.nic.uk, nsa.nic.uk, nsb.nic.uk, nsc.nic.uk, nsd.nic.uk
4
ns-1929.awsdns-49.co.uk
NS
dns1.nic.uk (2a01:618:400::1)

Answer: g-ns-1524.awsdns-49.co.uk, g-ns-1845.awsdns-49.co.uk, g-ns-369.awsdns-49.co.uk, g-ns-945.awsdns-49.co.uk

Answer: g-ns-1524.awsdns-49.co.uk
205.251.197.244, 2600:9000:5305:f400::1

Answer: g-ns-1845.awsdns-49.co.uk
205.251.199.53, 2600:9000:5307:3500::1

Answer: g-ns-369.awsdns-49.co.uk
205.251.193.113, 2600:9000:5301:7100::1

Answer: g-ns-945.awsdns-49.co.uk
205.251.195.177, 2600:9000:5303:b100::1
5
com
NS
k.root-servers.net (2001:7fd::1)

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
6
ns-286.awsdns-35.com
NS
e.gtld-servers.net (2001:502:1ca1::30)

Answer: g-ns-1187.awsdns-35.com, g-ns-1763.awsdns-35.com, g-ns-36.awsdns-35.com, g-ns-611.awsdns-35.com

Answer: g-ns-1187.awsdns-35.com
205.251.196.163, 2600:9000:5304:a300::1

Answer: g-ns-1763.awsdns-35.com
205.251.198.227, 2600:9000:5306:e300::1

Answer: g-ns-36.awsdns-35.com
205.251.192.36, 2600:9000:5300:2400::1

Answer: g-ns-611.awsdns-35.com
205.251.194.99, 2600:9000:5302:6300::1
7
net
NS
b.root-servers.net (2001:500:200::b)

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
8
ns-630.awsdns-14.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: g-ns-1358.awsdns-14.net, g-ns-1934.awsdns-14.net, g-ns-463.awsdns-14.net, g-ns-784.awsdns-14.net

Answer: g-ns-1358.awsdns-14.net
205.251.197.78, 2600:9000:5305:4e00::1

Answer: g-ns-1934.awsdns-14.net
205.251.199.142, 2600:9000:5307:8e00::1

Answer: g-ns-463.awsdns-14.net
205.251.193.207, 2600:9000:5301:cf00::1

Answer: g-ns-784.awsdns-14.net
205.251.195.16, 2600:9000:5303:1000::1
9
ns-1058.awsdns-04.org: 205.251.196.34
A
g-ns-1031.awsdns-04.org (2600:9000:5304:700::1)
10
ns-1058.awsdns-04.org: 2600:9000:5304:2200::1
AAAA
g-ns-1031.awsdns-04.org (2600:9000:5304:700::1)
11
ns-1929.awsdns-49.co.uk: 205.251.199.137
A
g-ns-1524.awsdns-49.co.uk (2600:9000:5305:f400::1)
12
ns-1929.awsdns-49.co.uk: 2600:9000:5307:8900::1
AAAA
g-ns-1524.awsdns-49.co.uk (2600:9000:5305:f400::1)
13
ns-286.awsdns-35.com: 205.251.193.30
A
g-ns-1187.awsdns-35.com (2600:9000:5304:a300::1)
14
ns-286.awsdns-35.com: 2600:9000:5301:1e00::1
AAAA
g-ns-1187.awsdns-35.com (2600:9000:5304:a300::1)
15
ns-630.awsdns-14.net: 205.251.194.118
A
g-ns-1358.awsdns-14.net (2600:9000:5305:4e00::1)
16
ns-630.awsdns-14.net: 2600:9000:5302:7600::1
AAAA
g-ns-1358.awsdns-14.net (2600:9000:5305:4e00::1)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
lomin.ai
0

no CAA entry found
1
0
ai
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
lomin.ai

ok
1
0
_acme-challenge.demo.lomin.ai.lomin.ai

Name Error - The domain name does not exist
1
0


15. DomainService - Entries

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=5a91ef65-1c1f-4c51-afc6-2742213e05cf


Last Result: https://check-your-website.server-daten.de/?q=demo.lomin.ai - 2024-04-17 15:08:53


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

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

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