TLD is not supported. >>> Last update of WHOIS database: 2025-12-19T15:20:34Z <<< Terms of Use: Access to WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the registry database. The data in this record is provided by Identity Digital or the Registry Operator for informational purposes only, and accuracy is not guaranteed. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Identity Digital except as reasonably necessary to register domain names or modify existing registrations. When using the Whois service, please consider the following: The Whois service is not a replacement for standard EPP commands to the SRS service. Whois is not considered authoritative for registered domain objects. The Whois service may be scheduled for downtime during production or OT&E maintenance periods. Queries to the Whois services are throttled. If too many queries are received from a single IP address within a specified time, the service will begin to reject further queries for a period of time to prevent disruption of Whois service access. Abuse of the Whois system through data mining is mitigated by detecting and limiting bulk query access from single sources. Where applicable, the presence of a [Non-Public Data] tag indicates that such data is not made publicly available due to applicable data privacy laws or requirements. Should you wish to contact the registrant, please refer to the Whois records available through the registrar URL listed above. Access to non-public data may be provided, upon request, where it can be re asonably confirmed that the requester holds a specific legitimate interest and a proper legal basis for accessing the withheld data. Access to this data provided by Identity Digital can be requested by submitting a request via the form found at https://www.identity.digital/about/policies/whois-layered-access/. The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Identity Digital Inc. and Registry Operator reserve the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.

discord.media has address 162.159.130.235 discord.media has address 162.159.129.235 discord.media has address 162.159.128.235 discord.media has address 162.159.137.234 discord.media has address 162.159.138.234 discord.media has IPv6 address 2606:4700:7::a29f:82eb discord.media has IPv6 address 2606:4700:7::a29f:80eb discord.media has IPv6 address 2606:4700:7::a29f:89ea discord.media has IPv6 address 2606:4700:7::a29f:8aea discord.media has IPv6 address 2606:4700:7::a29f:81eb

; <<>> DiG 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.9 <<>> discord.media ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9211 ;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;discord.media. IN A ;; ANSWER SECTION: discord.media. 207 IN A 162.159.137.234 discord.media. 207 IN A 162.159.130.235 discord.media. 207 IN A 162.159.138.234 discord.media. 207 IN A 162.159.128.235 discord.media. 207 IN A 162.159.129.235 ;; Query time: 5 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Fri Dec 19 15:22:37 UTC 2025 ;; MSG SIZE rcvd: 122

Server: 8.8.8.8 Address: 8.8.8.8#53 Non-authoritative answer: Name: discord.media Address: 162.159.137.234 Name: discord.media Address: 162.159.129.235 Name: discord.media Address: 162.159.138.234 Name: discord.media Address: 162.159.130.235 Name: discord.media Address: 162.159.128.235 Name: discord.media Address: 2606:4700:7::a29f:80eb Name: discord.media Address: 2606:4700:7::a29f:8aea Name: discord.media Address: 2606:4700:7::a29f:81eb Name: discord.media Address: 2606:4700:7::a29f:82eb Name: discord.media Address: 2606:4700:7::a29f:89ea

PING discord.media (162.159.138.234) 56(84) bytes of data. 64 bytes from 162.159.138.234 (162.159.138.234): icmp_seq=1 ttl=55 time=4.27 ms 64 bytes from 162.159.138.234 (162.159.138.234): icmp_seq=2 ttl=55 time=4.07 ms 64 bytes from 162.159.138.234 (162.159.138.234): icmp_seq=3 ttl=55 time=4.21 ms --- discord.media ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 4.077/4.187/4.270/0.096 ms

traceroute to discord.media (162.159.129.235), 30 hops max, 60 byte packets 1 gateway (172.31.1.1) 2.853 ms 3.182 ms 3.279 ms 2 21739.your-cloud.host (49.12.143.167) 0.612 ms 0.636 ms 0.635 ms 3 * * * 4 * * * 5 spine16.cloud1.nbg1.hetzner.com (85.10.237.165) 1.364 ms spine15.cloud1.nbg1.hetzner.com (213.133.114.57) 1.441 ms spine15.cloud1.nbg1.hetzner.com (213.133.114.49) 1.428 ms 6 core12.nbg1.hetzner.com (213.239.203.105) 1.757 ms 1.134 ms 1.081 ms 7 core5.fra.hetzner.com (213.239.224.238) 4.079 ms core0.fra.hetzner.com (213.239.252.21) 3.445 ms core4.fra.hetzner.com (213.239.245.33) 3.628 ms 8 core8.fra.hetzner.com (213.239.252.9) 3.809 ms core8.fra.hetzner.com (213.239.245.126) 3.630 ms 3.662 ms 9 162.158.84.254 (162.158.84.254) 40.489 ms static.213-133-112-34.clients.your-server.de (213.133.112.34) 4.696 ms 162.158.84.254 (162.158.84.254) 11.809 ms 10 162.158.84.56 (162.158.84.56) 13.041 ms 162.158.84.1 (162.158.84.1) 4.833 ms 162.158.84.56 (162.158.84.56) 13.030 ms 11 162.158.84.173 (162.158.84.173) 4.975 ms 162.158.84.123 (162.158.84.123) 13.135 ms 162.158.84.145 (162.158.84.145) 8.980 ms 12 162.159.129.235 (162.159.129.235) 4.725 ms 4.714 ms 4.029 ms

An error occurred. This command accepts IP addresses only. You can use nslookup to get the addresses of discord.media