Skip to content

Hostname

serveroyun.com

Last fetched

serveroyun.com resolves to 104.21.64.13, announced in 104.21.64.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. serveroyun.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · serveroyun.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/serveroyun.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:303
Registrant organisation
domain admin
Contact emails
admin@serveroyun.com, serveroyun.com@domainsbyproxy.com, contact@privacyprotect.org

Subdomains

Subdomain
blog.serveroyun.com
cp1.serveroyun.com
cp2.serveroyun.com
cpanel.serveroyun.com
cpanel1.serveroyun.com
cpanel2.serveroyun.com
diyo.serveroyun.com
forum.serveroyun.com
game.serveroyun.com
gpanel.serveroyun.com
mail.serveroyun.com
manage.serveroyun.com

Showing 12 of 23. View all subdomains →

Mail and authentication

Nameservers

  • henrik.ns.cloudflare.com
  • ryleigh.ns.cloudflare.com
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • mremium2.guzelhosting.com
  • mt-spamexperts.guzel.net.tr
  • ni-spamexperts.guzel.net.tr
  • pmg.guzel.net.tr
  • pmg2.guzel.net.tr

SPF policy

  • include: _spf.google.com
  • include: relay.guzelhosting.com
  • a: serveroyun.com
  • mx: serveroyun.com
  • ip: 151.242.52.12

Threat-feed evidence

History

Related pages

Pivot from serveroyun.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "serveroyun.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.