Skip to content

Hostname

roomlala.com

Last fetched

roomlala.com resolves to 158.255.65.79, announced in 158.255.64.0/21 by OXEVA - Oxeva SAS in FR. roomlala.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 · roomlala.comRouting diversity1.5/10Peering density4.8/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/roomlala.com

Resolution chain

IPv6 resolution

Attribution

oxeva

ORIGIN_AS

WHOIS identity

Registrar
iana:81
Registrant organisation
philippe de rouville
Contact emails
735c8e7ff80a0de6a414f5dfe1528c2e-1867747@contact.gandi.net, 97b5af7ab1fdfa13395d82948793c393-1867747@contact.gandi.net, e9187651b995f2a7ef94543bb0eb55cb-1867747@contact.gandi.net

Subdomains

Subdomain
ca-mn.roomlala.com
cdn-media.roomlala.com
de-at.roomlala.com
de-ca.roomlala.com
de-ch.roomlala.com
de-de.roomlala.com
de-tr.roomlala.com
email.roomlala.com
en-at.roomlala.com
en-au.roomlala.com
en-ca.roomlala.com
en-ch.roomlala.com

Showing 12 of 49. 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

Mail and authentication

Nameservers

  • ns-212-a.gandi.net
  • ns-55-b.gandi.net
  • ns-60-c.gandi.net
  • ns1.gandi.net

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com

SPF policy

  • a: google.com
  • include: spf.mailjet.com
  • include: spf.mandrillapp.com
  • a: roomlala.com
  • mx: roomlala.com
  • include: trustpilotservice.com
  • include: servers.mcsv.net
  • ip: 62.4.22.122

Threat-feed evidence

History

Related pages

Pivot from roomlala.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: "roomlala.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.