Skip to content

Hostname

royalehosting.net

Last fetched

royalehosting.net resolves to 104.26.0.99, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. royalehosting.net 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 · royalehosting.netRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint3.2/10canon.whisper.security/host/royalehosting.net

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:168
Registrant organisation
royalehosting b.v.
Contact emails
11050b02f5a9426691ed8532db9f5655.protect@whoisguard.com, 22a68b7cd60048dc836a850a22781c45.protect@withheldforprivacy.com, d628525033be451ca786fa9c9a82ab5b.protect@withheldforprivacy.com, stanvandeklippe@gmail.com, asmli4lz3r@domprivacy.de, stan@royalehosting.nl

Subdomains

Subdomain
beta.royalehosting.net
blog.royalehosting.net
dev.royalehosting.net
game.royalehosting.net
game02.royalehosting.net
gitlab.royalehosting.net
inventory.royalehosting.net
kb.royalehosting.net
mail.royalehosting.net
manager.royalehosting.net
mydev.royalehosting.net
ns1.royalehosting.net

Showing 12 of 30. View all subdomains →

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • ivy.ns.cloudflare.com
  • will.ns.cloudflare.com

MX records

  • mail.royalehosting.nl

SPF policy

  • ip: 185.104.29.0/24
  • a: royalehosting.net
  • mx: royalehosting.net
  • include: sendgrid.net
  • include: filter-out.zxcs.nl
  • ip: 185.104.29.56
  • ip: 2a06:2ec0:1:0:0:0:0:105

Threat-feed evidence

History

Related pages

Pivot from royalehosting.net 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: "royalehosting.net"})-[: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.