Skip to content

Hostname

beoffices.com

Last fetched

beoffices.com has no current public IPv4 resolution in WhisperGraph; WHOIS lists iana:2 as the registrar.

Nutrition Label

WHISPER CANON · beoffices.comRouting diversity—Peering density—MOAS conflict—Threat-feed listings—WHOIS transparency—Resolver footprint—canon.whisper.security/host/beoffices.com

Resolution chain

beoffices.com has no current public IPv4 resolution in WhisperGraph. The WHOIS record below is the only graph data we have on this hostname.

WHOIS identity

Registrar
iana:2
Organization
majestic business centres limited attn beoffices.com care of network solutions
Contact emails

Subdomains

18 observed subdomains of beoffices.com.

Subdomain
andmeetings.beoffices.com
www.beoffices.com
wildcard.beoffices.com
status.beoffices.com
royalx.beoffices.com
reading.beoffices.com
mx2.beoffices.com
mkbeg.beoffices.com
mail1.beoffices.com
mail.beoffices.com
gordonhouse.beoffices.com
email.beoffices.com
begmk2.beoffices.com
begmk.beoffices.com
beechstreet.beoffices.com
beech.beoffices.com
autodiscover.beoffices.com

Showing 17 of 18. View all subdomains →

Web-graph footprint

Distinct hostnames that link to or from beoffices.com in the public web crawl.

Sample inbound links

Threat posture

History

Mail and authentication

MX records

SPF policy

23 SPF mechanisms authorising senders for beoffices.com.

MechanismTarget
SPF_Abeoffices.com
SPF_INCLUDE_netblocks.mimecast.com
SPF_INCLUDEspf.protection.outlook.com
SPF_IP151.237.234.60/32
SPF_IP151.237.235.158/32
SPF_IP185.151.30.121/15
SPF_IP185.19.208.121/32
SPF_IP194.168.187.67/32
SPF_IP194.168.187.78/32
SPF_IP194.168.187.82/32
SPF_IP194.168.187.84/32
SPF_IP212.64.132.76/32
SPF_IP213.48.61.135/32
SPF_IP31.221.36.66/32
SPF_IP51.77.241.56/32
SPF_IP54.38.15.128/32
SPF_IP80.193.232.55/32
SPF_IP80.194.101.202/32
SPF_IP82.33.245.5/32
SPF_IP82.33.245.71/32
SPF_IP89.197.149.128/26
SPF_IP94.175.242.139/32
SPF_MXbeoffices.com

Related pages

Pivot deeper into the graph from beoffices.com.

Cypher and MCP

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

MATCH (h:HOSTNAME {name: "beoffices.com"})-[: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.