--- Begin Message ---
Hmm, interesting.

Whois services I have tried did not include that address. I tried even web interface, but it was empty.

Sent there a request to upgrade their algorithm. Should not be difficult when it is supposed to fail anyway.

On 18/11/2025 21:26, Warren Kumari wrote:



Have you tried: [email protected] ?

WHOIS was actually helpful for once :-)


Here's what we found:
Registrar Name
        GoDaddy Corporate Domains, LLC
Registrar IANA
        
Registrar URL
        https://gcd.com
Registrar WHOIS Server
        whois.brandsight.com <http://whois.brandsight.com/>
Statuses
        clientTransferProhibited
Nameservers
dns101.comcast.net <http://dns101.comcast.net/>, dns102.comcast.net <http://dns102.comcast.net/>, dns103.comcast.net <http://dns103.comcast.net/>, dns104.comcast.net <http://dns104.comcast.net/>, dns105.comcast.net <http://dns105.comcast.net/>
DNSSEC
        
Registrant Name
        Comcast Domains
Registrant Email
        [email protected]
Created Date
        2010-Oct-15
Updated Date
        2025-Sep-14
Expire Date
        2026-Oct-15




On Tue, Nov 18, 2025 at 11:30 AM, Scott Morizot <[email protected]> wrote:

    I vaguely recall that Comcast set up the service ages ago. No idea
    on current contact info, though.

    On Tue, Nov 18, 2025, 07:06 Petr Menšík via dns-operations
    <[email protected] <mailto:[email protected]>>
    wrote:




        ---------- Forwarded message ----------
        From: "Petr Menšík" <[email protected]
        <mailto:[email protected]>>
        To: [email protected]
        <mailto:[email protected]>
        Cc:
        Bcc:
        Date: Tue, 18 Nov 2025 13:58:47 +0100
        Subject: dnssec-failed.org <http://dnssec-failed.org> operator
        contact
        Hi!

        Would you know how to find correct contact information for
        dnssec-failed.org <http://dnssec-failed.org> service? It is
        service with a nice name and our Red
        Hat Enterprise Linux customers are often confused, why it is
        not failing
        when they enable dnssec validation on their host.

        It would help if operator of this domain used some different
        algorithm
        than SHA-1 base algorithm 5. It should be simple to roll to
        any more
        recent algorithm, which is still considered secure by everyone.

        Whois query did not reveal any contact information. Do you
        know any
        other contact information for this service?

-- Petr Menšík
        Software Engineer, RHEL
        Red Hat, https://www.redhat.com/ <https://www.redhat.com/>
        PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB




        ---------- Forwarded message ----------
        From: "Petr Menšík via dns-operations"
        <[email protected] <mailto:[email protected]>>
        To: [email protected]
        <mailto:[email protected]>
        Cc:
        Bcc:
        Date: Tue, 18 Nov 2025 13:58:47 +0100
        Subject: [dns-operations] dnssec-failed.org
        <http://dnssec-failed.org> operator contact
        _______________________________________________
        dns-operations mailing list
        [email protected]
        <mailto:[email protected]>
        https://lists.dns-oarc.net/mailman/listinfo/dns-operations
        <https://lists.dns-oarc.net/mailman/listinfo/dns-operations>

    _______________________________________________
    dns-operations mailing list
    [email protected]
    <mailto:[email protected]>
    https://lists.dns-oarc.net/mailman/listinfo/dns-operations
    <https://lists.dns-oarc.net/mailman/listinfo/dns-operations>


--
Petr Menšík
Software Engineer, RHEL
Red Hat,https://www.redhat.com/
PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB

--- End Message ---
_______________________________________________
dns-operations mailing list
[email protected]
https://lists.dns-oarc.net/mailman/listinfo/dns-operations

Reply via email to