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


 

 

U

 

No dns entry found - perhaps mistype. Or wrong IDN

 

Checked:
30.10.2024 15:57:56

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
mfa.pleuneservice.om

Name Error
yes
1
0
www.mfa.pleuneservice.om

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






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 11.11.2024, 00:00:00 +, Signature-Inception: 21.10.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: om

om
0 DS RR in the parent zone found






DS-Query in the parent zone has a valid NSEC RR as result with the domain name between the NSEC-Owner "om" and the NextOwner "omega". So the parent zone confirmes the non-existence of a DS RR.
Bitmap: NS, RRSIG, NSEC






3 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 10791, Flags 256






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






Public Key with Algorithm 8, KeyTag 60906, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner om., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 09.11.2024, 05:56:28 +, Signature-Inception: 26.10.2024, 04:56:41 +, KeyTag 20359, Signer-Name: om






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






Error: DNSKEY 20359 signs DNSKEY RRset, but no confirming DS RR in the parent zone found. No chain of trust created.



Zone: pleuneservice.om

pleuneservice.om
0 DS RR in the parent zone found






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7" as Owner. That's the Hash of "om" with the NextHashedOwnerName "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7". So that domain name is the Closest Encloser of "pleuneservice.om". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS, CDNSKEY Validated: RRSIG-Owner q80i2o2p6csfqpoobh5l8s8jvhhdpqt7.om., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 09.11.2024, 05:56:28 +, Signature-Inception: 26.10.2024, 04:56:41 +, KeyTag 10791, Signer-Name: om






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7" as Owner. That's the Hash of "om" with the NextHashedOwnerName "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7". So that domain name is the Closest Encloser of "pleuneservice.om". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS, CDNSKEY Validated: RRSIG-Owner q80i2o2p6csfqpoobh5l8s8jvhhdpqt7.om., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 09.11.2024, 05:56:28 +, Signature-Inception: 26.10.2024, 04:56:41 +, KeyTag 60906, Signer-Name: om






The ClosestEncloser says, that "*.om" with the Hash "4p23cjhi3vjhfoasnuurb8rdicpljg9n" 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 "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7" and the Next Owner "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS, CDNSKEY Validated: RRSIG-Owner q80i2o2p6csfqpoobh5l8s8jvhhdpqt7.om., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 09.11.2024, 05:56:28 +, Signature-Inception: 26.10.2024, 04:56:41 +, KeyTag 10791, Signer-Name: om






The ClosestEncloser says, that "*.om" with the Hash "4p23cjhi3vjhfoasnuurb8rdicpljg9n" 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 "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7" and the Next Owner "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS, CDNSKEY Validated: RRSIG-Owner q80i2o2p6csfqpoobh5l8s8jvhhdpqt7.om., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 09.11.2024, 05:56:28 +, Signature-Inception: 26.10.2024, 04:56:41 +, KeyTag 60906, Signer-Name: om






The NSEC3-Owner "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7" is the same as the NextHashedOwnerName. So the parent zone has only this one domain name and doesn't allow secure delegations. Conclusion: It's impossible to use DNSSEC with that parent zone.






The NSEC3-Owner "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7" is the same as the NextHashedOwnerName. So the parent zone has only this one domain name and doesn't allow secure delegations. Conclusion: It's impossible to use DNSSEC with that parent zone.



Zone: mfa.pleuneservice.om

mfa.pleuneservice.om
0 DS RR in the parent zone found






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7" as Owner. That's the Hash of "om" with the NextHashedOwnerName "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7". So that domain name is the Closest Encloser of "mfa.pleuneservice.om". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS, CDNSKEY Validated: RRSIG-Owner q80i2o2p6csfqpoobh5l8s8jvhhdpqt7.om., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 09.11.2024, 05:56:28 +, Signature-Inception: 26.10.2024, 04:56:41 +, KeyTag 10791, Signer-Name: om






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7" as Owner. That's the Hash of "om" with the NextHashedOwnerName "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7". So that domain name is the Closest Encloser of "mfa.pleuneservice.om". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS, CDNSKEY Validated: RRSIG-Owner q80i2o2p6csfqpoobh5l8s8jvhhdpqt7.om., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 09.11.2024, 05:56:28 +, Signature-Inception: 26.10.2024, 04:56:41 +, KeyTag 60906, Signer-Name: om






The ClosestEncloser says, that "*.om" with the Hash "4p23cjhi3vjhfoasnuurb8rdicpljg9n" 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 "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7" and the Next Owner "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS, CDNSKEY Validated: RRSIG-Owner q80i2o2p6csfqpoobh5l8s8jvhhdpqt7.om., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 09.11.2024, 05:56:28 +, Signature-Inception: 26.10.2024, 04:56:41 +, KeyTag 10791, Signer-Name: om






The ClosestEncloser says, that "*.om" with the Hash "4p23cjhi3vjhfoasnuurb8rdicpljg9n" 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 "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7" and the Next Owner "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS, CDNSKEY Validated: RRSIG-Owner q80i2o2p6csfqpoobh5l8s8jvhhdpqt7.om., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 09.11.2024, 05:56:28 +, Signature-Inception: 26.10.2024, 04:56:41 +, KeyTag 60906, Signer-Name: om






The NSEC3-Owner "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7" is the same as the NextHashedOwnerName. So the parent zone has only this one domain name and doesn't allow secure delegations. Conclusion: It's impossible to use DNSSEC with that parent zone.






The NSEC3-Owner "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7" is the same as the NextHashedOwnerName. So the parent zone has only this one domain name and doesn't allow secure delegations. Conclusion: It's impossible to use DNSSEC with that parent zone.



Zone: www.mfa.pleuneservice.om

www.mfa.pleuneservice.om
0 DS RR in the parent zone found






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7" as Owner. That's the Hash of "om" with the NextHashedOwnerName "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7". So that domain name is the Closest Encloser of "www.mfa.pleuneservice.om". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS, CDNSKEY Validated: RRSIG-Owner q80i2o2p6csfqpoobh5l8s8jvhhdpqt7.om., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 09.11.2024, 05:56:28 +, Signature-Inception: 26.10.2024, 04:56:41 +, KeyTag 10791, Signer-Name: om






DS-Query in the parent zone sends valid NSEC3 RR with the Hash "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7" as Owner. That's the Hash of "om" with the NextHashedOwnerName "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7". So that domain name is the Closest Encloser of "www.mfa.pleuneservice.om". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS, CDNSKEY Validated: RRSIG-Owner q80i2o2p6csfqpoobh5l8s8jvhhdpqt7.om., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 09.11.2024, 05:56:28 +, Signature-Inception: 26.10.2024, 04:56:41 +, KeyTag 60906, Signer-Name: om






The ClosestEncloser says, that "*.om" with the Hash "4p23cjhi3vjhfoasnuurb8rdicpljg9n" 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 "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7" and the Next Owner "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS, CDNSKEY Validated: RRSIG-Owner q80i2o2p6csfqpoobh5l8s8jvhhdpqt7.om., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 09.11.2024, 05:56:28 +, Signature-Inception: 26.10.2024, 04:56:41 +, KeyTag 10791, Signer-Name: om






The ClosestEncloser says, that "*.om" with the Hash "4p23cjhi3vjhfoasnuurb8rdicpljg9n" 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 "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7" and the Next Owner "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM, CDS, CDNSKEY Validated: RRSIG-Owner q80i2o2p6csfqpoobh5l8s8jvhhdpqt7.om., Algorithm: 8, 2 Labels, original TTL: 3600 sec, Signature-expiration: 09.11.2024, 05:56:28 +, Signature-Inception: 26.10.2024, 04:56:41 +, KeyTag 60906, Signer-Name: om






The NSEC3-Owner "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7" is the same as the NextHashedOwnerName. So the parent zone has only this one domain name and doesn't allow secure delegations. Conclusion: It's impossible to use DNSSEC with that parent zone.






The NSEC3-Owner "q80i2o2p6csfqpoobh5l8s8jvhhdpqt7" is the same as the NextHashedOwnerName. So the parent zone has only this one domain name and doesn't allow secure delegations. Conclusion: It's impossible to use DNSSEC with that parent zone.

 

3. Name Servers

DomainNameserverNS-IP
www.mfa.pleuneservice.om
  ns1.registry.om

mfa.pleuneservice.om
  ns1.registry.om

pleuneservice.om
  ns1.registry.om

om
  cctld.alpha.aridns.net.au / dns1.defra1


  cctld.beta.aridns.net.au / dns3.defra1


  cctld.delta.aridns.net.au / dns4.defra1


  cctld.gamma.aridns.net.au / dns3.defra1


X  ns1.registry.om / dns2.pri.omregistry.local


X  ns2.registry.om / dns2.sec.omregistry.local

 

4. SOA-Entries


Domain:om
Zone-Name:om
Primary:ns1.registry.om
Mail:dnsmanager.tra.gov.om
Serial:1730294539
Refresh:86400
Retry:7200
Expire:3600000
TTL:3600
num Entries:6


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


Domain:mfa.pleuneservice.om
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:www.mfa.pleuneservice.om
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 "mfa.pleuneservice.om" is subdomain, public suffix is ".om", top-level-domain is ".om", top-level-domain-type is "country-code", Country is Oman, tld-manager is "Telecommunications Regulatory Authority (TRA)", num .om-domains preloaded: 9 (complete: 251685)
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.
XFatal error: Nameserver doesn't support TCP connection: ns1.registry.om: Fatal error (-14). Details: Unable to read data from the transport connection: Eine vorhandene Verbindung wurde vom Remotehost geschlossen.. - Eine vorhandene Verbindung wurde vom Remotehost geschlossen.
XFatal error: Nameserver doesn't support TCP connection: ns2.registry.om: Fatal error (-14). Details: Unable to read data from the transport connection: Eine vorhandene Verbindung wurde vom Remotehost geschlossen.. - Eine vorhandene Verbindung wurde vom Remotehost geschlossen.
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.mfa.pleuneservice.om

2. Header-Checks (Cross-Origin-* headers are alpha - started 2024-06-05)

U

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

3. DNS- and NameServer - Checks

A
A
AInfo:: 6 different Name Servers found: cctld.alpha.aridns.net.au, cctld.beta.aridns.net.au, cctld.delta.aridns.net.au, cctld.gamma.aridns.net.au, ns1.registry.om, ns2.registry.om, 6 Name Servers included in Delegation: cctld.alpha.aridns.net.au, cctld.beta.aridns.net.au, cctld.delta.aridns.net.au, cctld.gamma.aridns.net.au, ns1.registry.om, ns2.registry.om, 6 Name Servers included in 1 Zone definitions: cctld.alpha.aridns.net.au, cctld.beta.aridns.net.au, cctld.delta.aridns.net.au, cctld.gamma.aridns.net.au, ns1.registry.om, ns2.registry.om, 1 Name Servers listed in SOA.Primary: ns1.registry.om.
AGood: Only one SOA.Primary Name Server found.: ns1.registry.om.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.registry.om.
AGood: All Name Server Domain Names have a Public Suffix.
A
Nameserver doesn't pass all EDNS-Checks: ns1.registry.om: 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: ns1.registry.om: 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: ns1.registry.om: 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: 28443 milliseconds, 28.443 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

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. Html-Parsing via https://validator.nu/ / https://validator.w3.org/nu/ (started 2024-09-28, 09:00, alpha)

  Unfortunately, there are differences between the first used validator.nu and validator.w3.org/nu/ - switched to validator.w3.org/nu/. Looks like some error messages (link - fetchpriority attribute) of validator.nu are obsolete, not seen in the w3.org-version and not found in the current specification: link may have a fetchpriority attribute.

No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

 

13. Nameserver - IP-Adresses

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

 

 

No NameServer - IP address - Informations found

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
om
0

no CAA entry found
1
0

 

15. TXT - Entries

No TXT entries found

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

No Ciphers found

 

18. Portchecks

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

 

 

Permalink: https://check-your-website.server-daten.de/?i=02c2b2ef-6647-4f82-a304-75b52eb930b1

 

Last Result: https://check-your-website.server-daten.de/?q=mfa.pleuneservice.om - 2024-10-30 15:57:56

 

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

 

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

 

 

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

 

QR-Code of this page - https://check-your-website.server-daten.de/?d=mfa.pleuneservice.om