Skip to content

Hostname

lemoncom.be

Last fetched

lemoncom.be resolves to 1 IPv4 address operated by AS16276 in FR. WHOIS lists registrar:ovh as the registrar.

Nutrition Label

WHISPER CANON · lemoncom.beRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency0.0/10Resolver footprint3.2/10canon.whisper.security/host/lemoncom.be

Resolution chain

lemoncom.be resolves to 1 distinct IPv4 address via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.

IPPrefixASNOperatorCountry
51.255.35.2952.18.0.0/15AS16276—FR

WHOIS identity

Registrar
registrar:ovh
Organization
—
Contact emails
—

Subdomains

15 observed subdomains of lemoncom.be.

Subdomain
mailing.lemoncom.be
maintenance.lemoncom.be
mgmt.lemoncom.be
webserver01.lemoncom.be
webserver02.lemoncom.be
webserver03.lemoncom.be
webserver04.lemoncom.be
webserver05.lemoncom.be
webserver06.lemoncom.be
webserver07.lemoncom.be
webserver08.lemoncom.be
webserver09.lemoncom.be
webserver10.lemoncom.be
webserver11.lemoncom.be
www.lemoncom.be

Web-graph footprint

Distinct hostnames that link to or from lemoncom.be in the public web crawl.

41 sites link to this hostname.

6 sites linked to from this hostname.

Sample inbound links

Sample outbound links

Threat posture

History

Mail and authentication

MX records

SPF policy

20 SPF mechanisms authorising senders for lemoncom.be.

MechanismTarget
SPF_Alemoncom.be
SPF_INCLUDE_spf.createsend.com
SPF_INCLUDEmx.ovh.com
SPF_IP141.94.69.200
SPF_IP141.95.158.194
SPF_IP141.95.158.195
SPF_IP141.95.158.197
SPF_IP141.95.158.199
SPF_IP146.59.198.234
SPF_IP2001:41d0:302:2100:0:0:0:87b
SPF_IP2001:41d0:302:2200:0:0:0:8ca
SPF_IP2001:41d0:304:200:0:0:0:814e
SPF_IP2001:41d0:304:200:0:0:0:814f
SPF_IP2001:41d0:304:200:0:0:0:8151
SPF_IP2001:41d0:304:200:0:0:0:8153
SPF_IP2001:41d0:304:200:0:0:0:9b4f
SPF_IP2001:41d0:304:200:0:0:0:cbfe
SPF_IP51.255.35.29
SPF_IP54.36.99.30
SPF_MXlemoncom.be

Related pages

Pivot deeper into the graph from lemoncom.be.

Cypher and MCP

Reproduce the resolution chain directly against graph.whisper.security:

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

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